search_registry
AI agents call search_registry to retrieve information from RunWhen Platform MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'search_registry' strongly indicates a retrieval operation against a registry. The verb 'search' is canonical for Read operations. With an empty description, confidence is reduced but not critically—the naming pattern is sufficiently clear when contextualized against sibling tools. No evidence of side effects, data modification, or irreversible actions.
From the tool's definition Tool named 'search_registry' with empty description; naming convention suggests querying/searching a registry without modification.
Attacks that exploit this kind of access
search_registry. It is categorised as a Read tool in the RunWhen Platform MCP MCP Server, which means it retrieves data without modifying state.
Register the RunWhen Platform MCP server in PolicyLayer and add a rule for 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 RunWhen Platform MCP. Nothing to install.
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 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 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.
search_registry is provided by the RunWhen Platform MCP server (runwhen-contrib/runwhen-platform-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 →