rapid7-mcp

get_asset_activity

Retrieve recent activity for an asset, including logins, processes, and network connections, to investigate incidents.

Instructions

Get recent activity for an asset including logins, processes, and network connections

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asset_id": "<asset_id>"
    },
    "name": "get_asset_activity"
  }
}

Input Schema

Name	Required	Description	Default
`size`	No	Number of activity records to return (1-100)
`asset_id`	Yes	Asset ID or RRN
`end_time`	No	Filter activity before this ISO 8601 timestamp
`start_time`	No	Filter activity after this ISO 8601 timestamp
`activity_type`	No	Type of activity to retrieve	ALL

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

B3.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden for behavioral disclosure. It only mentions 'recent activity' without defining recency (e.g., default time range, sorting order). It fails to describe pagination, result limits, or behavior for multiple activity types. This lack of detail is a significant gap for a tool with 5 parameters and no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence includes the verb, resource, and key included elements. No extraneous words; the description is efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 5 parameters, no output schema, and moderate complexity, the description lacks critical information such as return format, ordering, time range defaults, and scope (single asset). It is too sparse to fully guide an agent that cannot infer from the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the schema already explains each parameter well. The description adds marginal value by grouping types (logins, processes, network connections) but does not enhance parameter understanding beyond schema defaults. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'asset activity', and explicitly lists included types (logins, processes, network connections). This distinguishes it from sibling tools like 'get_asset' (details) and 'search_assets' (search), making the purpose specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when needing recent activity for a specific asset, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., 'search_asset_activity' or log-based tools). No exclusions or conditions are stated, leaving the agent to infer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.