Analyze blast radius for an indexed symbol or file using reverse repo graph traversal. Returns callers, upstream affected symbols, and suggested tests.
AI agents call repo.impact to retrieve information from Lore Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis and graph traversal to understand dependencies and impact, with no mutation, deletion, code execution, or financial operations. It queries an indexed symbol database and reports findings, making it a read-only operation with minimal risk if misused by an AI agent.
From the tool's definition Tool description states it 'Analyze blast radius' and 'Returns callers, upstream affected symbols, and suggested tests' — all read operations that retrieve and report information without modifying data.
Attacks that exploit this kind of access
Analyze blast radius for an indexed symbol or file using reverse repo graph traversal. Returns callers, upstream affected symbols, and suggested tests. It is categorised as a Read tool in the Lore Context MCP Server, which means it retrieves data without modifying state.
Register the Lore Context MCP server in PolicyLayer and add a rule for repo.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 Lore Context. Nothing to install.
repo.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 repo.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 repo.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.
repo.impact is provided by the Lore Context MCP server (Lore-Context/lore-context). 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 →