Analyse the impact of code changes. Accepts explicit file paths or auto-detects from git diff. Returns impacted entities classified by risk level (CRITICAL/HIGH/MEDIUM/LOW) with affected tests. Call this before making changes to understand what else might break, or after changes to identify what ...
AI agents call get_blast_radius to retrieve information from Rails Insight without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only analysis tool that examines codebase structure and git diffs to provide impact assessment information. It has no side effects, does not execute code, and does not modify any data. The low severity reflects that misuse would only provide inaccurate analysis output without risking damage to systems or data.
From the tool's definition Tool performs 'Analyse the impact' and 'Returns impacted entities' — it retrieves and queries data about potential code change impacts. No modifications, deletions, or external operations are triggered.
Attacks that exploit this kind of access
Analyse the impact of code changes. Accepts explicit file paths or auto-detects from git diff. Returns impacted entities classified by risk level (CRITICAL/HIGH/MEDIUM/LOW) with affected tests. Call this before making changes to understand what else might break, or after changes to identify what needs testing. It is categorised as a Read tool in the Rails Insight MCP Server, which means it retrieves data without modifying state.
Register the Rails Insight 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 Rails Insight. 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 Rails Insight MCP server (@reinteractive/rails-insight). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_blast_radius is one line of Rails Insight's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →