Blast radius and dependency analysis. Given a symbol (by name or node_id), returns all transitive dependents and the dependency paths explaining each. Replaces the need for separate find_symbol + explain_impact calls.
AI agents call explain_impact to retrieve information from Knocoph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
explain_impact performs a read-only query operation on the SQLite knowledge graph to analyze and retrieve dependency relationships. It has no capability to modify, delete, or execute code. The blast radius of misuse is limited to potential information disclosure about codebase structure, which is low severity.
From the tool's definition The tool 'returns all transitive dependents and the dependency paths' — it queries and retrieves dependency information from the code knowledge graph without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
Blast radius and dependency analysis. Given a symbol (by name or node_id), returns all transitive dependents and the dependency paths explaining each. Replaces the need for separate find_symbol + explain_impact calls. It is categorised as a Read tool in the Knocoph MCP Server, which means it retrieves data without modifying state.
Register the Knocoph MCP server in PolicyLayer and add a rule for explain_impact: 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 Knocoph. Nothing to install.
explain_impact 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 explain_impact 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 explain_impact. 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.
explain_impact is provided by the Knocoph MCP server (jagonzalr/knocoph). 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 →