AI agents call get-searcher-by-searcher-name-query to retrieve information from Mcp Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves search results from an existing searcher without modifying, deleting, or executing arbitrary code. It is a straightforward read operation that queries data and returns results. The low severity reflects minimal blast radius if misused—an AI agent could retrieve sensitive information through searches, but cannot modify system state or execute arbitrary operations.
From the tool's definition Tool name contains 'get' and 'query'; description states 'Gets search results' and 'Returns search results' with no mention of modification, deletion, or execution of arbitrary operations. The pagination support further indicates a pure retrieval operation.
Attacks that exploit this kind of access
Gets search results from a specific searcher by name with query parameters. Returns search results from the specified searcher with pagination support. It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for get-searcher-by-searcher-name-query: 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 Mcp Dev. Nothing to install.
get-searcher-by-searcher-name-query 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 get-searcher-by-searcher-name-query 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 get-searcher-by-searcher-name-query. 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.
get-searcher-by-searcher-name-query is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). 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 →