Search the public MCP Registry for external servers not in the local manifest.
AI agents call gateway.search_registry to retrieve information from PMCP 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 operation against a public registry to discover metadata about MCP servers. It has no side effects, does not modify any data, does not execute code, does not create financial obligations, and does not destroy information. The only capability is retrieving and querying existing registry data, making it a straightforward Read operation with low risk.
From the tool's definition Tool description explicitly states 'Search the public MCP Registry' — a read-only query operation that retrieves information about available servers without modifying, deleting, or executing external code.
Documented attack patterns abuse exactly the kind of access gateway.search_registry gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for gateway.search_registry:
{
"version": "1",
"default": "deny",
"tools": {
"gateway.search_registry": {}
}
}gateway.search_registry 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 the public MCP Registry for external servers not in the local manifest. It is categorised as a Read tool in the PMCP MCP Server, which means it retrieves data without modifying state.
Register the P MCP server in PolicyLayer and add a rule for gateway.search_registry: 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 PMCP. Nothing to install.
gateway.search_registry 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 gateway.search_registry 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 gateway.search_registry. 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.
gateway.search_registry is provided by the P MCP server (viperjuice/pmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PMCP, 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.
26 PMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.