AI agents use create_investigation to create or update resources in Rapid7 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rapid7 environment.
This tool creates new data (investigation records) in the SIEM platform, making it a Write operation. It is reversible (investigations can typically be closed/archived), so it does not qualify as Destructive. Severity is medium because miscreating investigations could clutter security workflows, trigger false alerts, or consume analyst resources, but lacks the blast radius of Execute or Financial operations.
From the tool's definition Tool name 'create_investigation' and description states it 'Create[s] a new InsightIDR investigation' — a data creation operation. Investigations are audit-tracked security records in SIEM systems.
Attacks that exploit this kind of access
Create a new InsightIDR investigation with a title, priority, and status. It is categorised as a Write tool in the Rapid7 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rapid7 MCP server in PolicyLayer and add a rule for create_investigation: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Rapid7. Nothing to install.
create_investigation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_investigation rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for create_investigation. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
create_investigation is provided by the Rapid7 MCP server (solomonneas/rapid7-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →