AI agents call search_users to retrieve information from Rapid7 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search query against user account data in InsightIDR, returning results without making any changes to data, executing commands, or triggering external operations. It is a non-destructive information retrieval operation, fitting the Read category with low severity due to the narrow scope of exposure (user directory information) and passive nature of the action.
From the tool's definition Tool name 'search_users' and description 'Search user accounts monitored by InsightIDR by name, email, domain, or department' indicate a query/retrieval operation with no modification or execution capabilities.
Attacks that exploit this kind of access
Search user accounts monitored by InsightIDR by name, email, domain, or department. It is categorised as a Read tool in the Rapid7 MCP Server, which means it retrieves data without modifying state.
Register the Rapid7 MCP server in PolicyLayer and add a rule for search_users: 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.
search_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_users 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 search_users. 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.
search_users 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 →