rapid7-mcp

get_user_activity

Retrieve user activity data including login times, locations, accessed assets, and anomalies to analyze behavior and detect threats.

Instructions

Get user behavior analytics data: login times, locations, accessed assets, and anomalies

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": {
      "user_id": "<user_id>"
    },
    "name": "get_user_activity"
  }
}

Input Schema

Name	Required	Description	Default
`size`	No	Number of activity records to return (1-100)
`user_id`	Yes	User 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

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only lists data types but does not mention whether the tool is read-only, performance characteristics, pagination behavior, or authentication requirements.

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

Conciseness4/5

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

Single sentence, direct and to the point. No wasted words, but could be slightly more structured with a brief list for clarity.

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?

Despite 5 parameters and no output schema, the description lacks key details such as default time range, pagination behavior, and the nature of 'anomalies'. Users may need to infer behavior from the parameter names and types.

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?

Schema description coverage is 100%, so the description adds no extra meaning beyond what the schema already provides. However, it could highlight the required user_id or explain the activity_type enum, but it does not. Baseline score of 3 per guidelines.

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

Purpose4/5

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

Description clearly states the tool retrieves user behavior analytics data listing specific fields (login times, locations, accessed assets, anomalies). However, it does not differentiate from sibling tools like get_asset_activity or search_users that may also involve user activity data.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as get_risky_users or search_users. No context about prerequisites or appropriate use cases.

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