Analyze the blast radius of changing a symbol. Traces all callers/dependents recursively to show everything that could break. Use BEFORE making changes to critical code.
AI agents call codexray_impact to retrieve information from CodeXRay without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a pre-built semantic knowledge graph to retrieve and analyze code dependency information. It traces relationships between symbols to provide insights about blast radius, but performs no mutations, deletions, executions, or financial operations. The output is informational (read-only) analysis intended to inform human decision-making before changes are made.
From the tool's definition Tool name 'codexray_impact' and description 'Analyze the blast radius of changing a symbol. Traces all callers/dependents recursively to show everything that could break.' — performs static analysis and tracing of code dependencies, returning information…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access codexray_impact gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeXRay, and nothing reaches the server without passing your rules. This is the rule we recommend for codexray_impact:
{
"version": "1",
"default": "deny",
"tools": {
"codexray_impact": {}
}
} codexray_impact 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.
Analyze the blast radius of changing a symbol. Traces all callers/dependents recursively to show everything that could break. Use BEFORE making changes to critical code. It is categorised as a Read tool in the CodeXRay MCP Server, which means it retrieves data without modifying state.
Register the CodeXRay MCP server in PolicyLayer and add a rule for codexray_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 CodeXRay. Nothing to install.
codexray_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 codexray_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 codexray_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.
codexray_impact is provided by the CodeXRay MCP server (neuralrays/codexray). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeXRay, 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.
16 CodeXRay tools catalogued and risk-classified — across an index of 43,000+ MCP servers.