AI agents call search-detections to retrieve information from Security Infrastructure MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries detection data from security platforms without modifying or executing anything. The 'search-' prefix and presence alongside similar query tools ('search-attributes', 'search-events') confirms it is a Read operation.
From the tool's definition Tool name 'search-detections' and context as a security infrastructure MCP server with sibling tools 'search-attributes' and 'search-events' indicate querying/retrieval capability.
Documented attack patterns abuse exactly the kind of access search-detections gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Security Infrastructure MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search-detections:
{
"version": "1",
"default": "deny",
"tools": {
"search-detections": {}
}
}search-detections is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search-detections. It is categorised as a Read tool in the Security Infrastructure MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Security Infrastructure MCP Server MCP server in PolicyLayer and add a rule for search-detections: 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 Security Infrastructure MCP Server. Nothing to install.
search-detections 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-detections 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-detections. 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-detections is provided by the Security Infrastructure MCP Server MCP server (jmstar85/securityinfrastructure). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Security Infrastructure MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Security Infrastructure MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.