AI agents call adr_impact to retrieve information from Mcp Adr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool searches through existing ADRs to find references to a specific component. This is a pure read/query operation that retrieves information without modifying, creating, or deleting any data.
From the tool's definition "Find all ADRs that mention a component" — this is a search/query operation with no side effects
Attacks that exploit this kind of access
Find all ADRs that mention a component. It is categorised as a Read tool in the Mcp Adr MCP Server, which means it retrieves data without modifying state.
Register the Mcp Adr MCP server in PolicyLayer and add a rule for adr_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 Mcp Adr. Nothing to install.
adr_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 adr_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 adr_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.
adr_impact is provided by the Mcp Adr MCP server (mauriziomocci/mcp-adr). 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 →