Get all files, routes, and domains affected by changing a specific file. Use before making changes to understand impact.
AI agents call get_blast_radius to retrieve information from Carto MCP Server 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 of a codebase to provide dependency and impact information. It has no side effects on the system—it queries existing project metadata and returns read-only results. The tool is explicitly designed for planning and understanding, not executing or modifying state.
From the tool's definition Tool retrieves and queries data about files, routes, and domains affected by changes. No modifications, deletions, or code execution occurs—it only returns analysis results to inform decision-making.
Documented attack patterns abuse exactly the kind of access get_blast_radius gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Carto MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_blast_radius:
{
"version": "1",
"default": "deny",
"tools": {
"get_blast_radius": {}
}
}get_blast_radius 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.
Get all files, routes, and domains affected by changing a specific file. Use before making changes to understand impact. It is categorised as a Read tool in the Carto MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Carto MCP Server 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 Carto MCP Server. 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 Carto MCP Server MCP server (theanshsonkar/carto). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 Carto MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
22 Carto MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.