AI agents call tool_registry to retrieve information from Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool provides informational access to a registry of available tools and their metadata. It performs no write, execute, destructive, or financial operations. While it reveals sensitive information about available capabilities (which could inform an attacker), the act of listing is fundamentally a read operation with no blast radius beyond information disclosure.
From the tool's definition Tool description states it 'Lists every MCP tool' — a retrieval operation with no modification or side effects. The phrase 'lists' and 'with its side effects' (describing what the tool reports, not what it does) indicates a query/read action.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Lists every MCP tool with its side effects and whether it requires user approval. It is categorised as a Read tool in the Context MCP Server, which means it retrieves data without modifying state.
Register the Context MCP server in PolicyLayer and add a rule for tool_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 Context. Nothing to install.
tool_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 tool_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 tool_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.
tool_registry is provided by the Context MCP server (vibhasdutta/context-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 →