Calculate impact of changes to a module
AI agents call get_blast_radius to retrieve information from Mcp Coordinator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves analytical information about potential impacts of changes. It does not execute changes, modify data, delete anything, or commit financial transactions. It is purely informational—analyzing and reporting impact data. The blast radius calculation itself is a read operation that queries module dependencies and relationships to generate an impact report.
From the tool's definition Tool name 'get_blast_radius' and description 'Calculate impact of changes to a module' indicate a query/analysis function. The verb 'calculate' and 'get' are read-only operations that retrieve and compute impact analysis without modifying state.
Attacks that exploit this kind of access
Calculate impact of changes to a module. It is categorised as a Read tool in the Mcp Coordinator MCP Server, which means it retrieves data without modifying state.
Register the Mcp Coordinator MCP server in PolicyLayer and add a rule for get_blast_radius: 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 Mcp Coordinator. Nothing to install.
get_blast_radius 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 get_blast_radius 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 get_blast_radius. 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.
get_blast_radius is provided by the Mcp Coordinator MCP server (swoofer/mcp-coordinator). 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 →