Score the blast radius of changing a Route
AI agents call api_impact to retrieve information from OpenCodeHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries or analyzes the impact of potential changes to a Route without executing the change itself. It retrieves impact metrics for decision-making purposes. No code is modified, deleted, or executed. This is a read-only analytical operation consistent with code intelligence and impact analysis tools that help agents understand consequences before acting.
From the tool's definition Tool name 'api_impact' and description 'Score the blast radius of changing a Route' indicate analysis/scoring of impact, not modification of code or routes themselves. The verb 'score' and 'blast radius' are analytical metrics, not actions that alter state.
Attacks that exploit this kind of access
Score the blast radius of changing a Route. It is categorised as a Read tool in the OpenCodeHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenCodeHub MCP Server MCP server in PolicyLayer and add a rule for api_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 OpenCodeHub MCP Server. Nothing to install.
api_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 api_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 api_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.
api_impact is provided by the OpenCodeHub MCP Server MCP server (theagenticguy/opencodehub). 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 →