get-searcher
Lists all searchers with pagination support. Returns an object containing: - total: Total number of searchers (number) - items: Array of searcher objects with name and isEnabled properties
This record as markdown: /tools/mcp-dev/get-searcher.md
What get-searcher does on Mcp Dev
AI agents call get-searcher to retrieve information from Mcp Dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get-searcher is rated Low
This tool retrieves and lists existing searcher configurations from the Umbraco CMS with pagination support. It has no side effects, does not modify any data, and merely exposes information about enabled searchers. This is a straightforward read operation with minimal security risk.
From the tool's definition Tool description states it 'Lists all searchers' and 'Returns an object containing total and items', which are query/retrieval operations with no modification capability.
Attacks that exploit this kind of access
The rule that runs get-searcher safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-searcher, this is the rule to start with:
get-searcher is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every get-searcher call is checked against it from then on.
Questions about get-searcher
Lists all searchers with pagination support. Returns an object containing: - total: Total number of searchers (number) - items: Array of searcher objects with name and isEnabled properties. 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: 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 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 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. 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 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.
More on Mcp Dev, and thousands of servers like it.
This server
Across the catalogue