Report the dependency impact of an Agda source file. Returns the direct + transitive sets in both directions: which files import this one (`dependents`) and which files this one imports (`dependencies`). Use this to pick the most-impactful upstream file to repair first when triaging a multi-file ...
Accepts file system path (file)
Part of the Agda MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke agda_impact to trigger processes or run actions in Agda. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
agda_impact can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
agda_impact:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Agda policy for all 71 tools.
Agents calling execute-class tools like agda_impact have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
agda_impact is one of the high-risk operations in Agda. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Report the dependency impact of an Agda source file. Returns the direct + transitive sets in both directions: which files import this one (`dependents`) and which files this one imports (`dependencies`). Use this to pick the most-impactful upstream file to repair first when triaging a multi-file failure. Cheap to call repeatedly — the graph is rebuilt from disk each invocation, so newly added files show up without a server restart. Lists are sorted; pass `limit` to cap each list (default 50, hard cap 500).. It is categorised as a Execute tool in the Agda MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for agda_impact. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Agda MCP server.
agda_impact is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the agda_impact rule in your Intercept 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 Intercept policy for agda_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.
agda_impact is provided by the Agda MCP server (agda-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept