Transitive closure of downstream nodes. Every node that would become stale
AI agents call what_breaks_if to retrieve information from Procurement Graph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the dependency graph to determine which nodes would be affected by a change (impact analysis). It computes a transitive closure, which is a read-only algorithmic operation on existing graph data. No data is created, modified, deleted, or written. No code execution, financial transactions, or destructive operations occur.
From the tool's definition Tool description: 'Transitive closure of downstream nodes. Every node that would become stale' — performs graph traversal and analysis to identify impacted dependencies without modifying any data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Transitive closure of downstream nodes. Every node that would become stale. It is categorised as a Read tool in the Procurement Graph MCP Server, which means it retrieves data without modifying state.
Register the Procurement Graph MCP server in PolicyLayer and add a rule for what_breaks_if: 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 Procurement Graph. Nothing to install.
what_breaks_if 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 what_breaks_if 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 what_breaks_if. 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.
what_breaks_if is provided by the Procurement Graph MCP server (mfbaig35r/procurement-graph). 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 →