Predicts blast radius of code changes before making them. USE WHEN: planning refactoring, renaming symbols, deleting code, or assessing risk. Returns: direct impacts (callers, references, subclasses), indirect impacts (2-level transitive), and CROSS-PROJECT impacts (consumers in other indexed pro...
Accepts URL/endpoint input (uri)
Part of the Codegraph MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call codegraph_analyze_impact to retrieve information from Codegraph without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though codegraph_analyze_impact only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
codegraph_analyze_impact:
rules:
- action: allowSee the full Codegraph policy for all 38 tools.
Agents calling read-class tools like codegraph_analyze_impact have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Predicts blast radius of code changes before making them. USE WHEN: planning refactoring, renaming symbols, deleting code, or assessing risk. Returns: direct impacts (callers, references, subclasses), indirect impacts (2-level transitive), and CROSS-PROJECT impacts (consumers in other indexed projects found via unresolved calls, type references, and #include tracking). Risk level is elevated when cross-project consumers exist. changeType affects analysis: 'modify' shows callers/dependents, 'delete' shows all references that would break, 'rename' shows all sites needing updates. Requires uri and line parameters.. It is categorised as a Read tool in the Codegraph MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for codegraph_analyze_impact. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Codegraph MCP server.
codegraph_analyze_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 codegraph_analyze_impact rule in your Intercept 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 Intercept policy for codegraph_analyze_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.
codegraph_analyze_impact is provided by the Codegraph MCP server (@memoryx/codegraph-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept