Remove redundant transitive edges (if A->B->C and A->C exist, remove A->C)
AI agents call transitive_reduction to permanently remove resources in Mcp Graph Engine — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes edges from the graph. While it operates according to a specific algorithm (transitive reduction), the removal of edges is a destructive operation that cannot be easily undone without a full backup. Misuse could silently destroy important direct relationships that were intentionally modeled, even if they are technically redundant from a graph theory perspective.
From the tool's definition Remove redundant transitive edges... remove A->C
Documented attack patterns abuse exactly the kind of access transitive_reduction gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Graph Engine, and nothing reaches the server without passing your rules. This is the rule we recommend for transitive_reduction:
{
"version": "1",
"default": "deny",
"hide": [
"transitive_reduction"
]
}transitive_reduction disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove redundant transitive edges (if A->B->C and A->C exist, remove A->C). It is categorised as a Destructive tool in the Mcp Graph Engine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Graph Engine MCP server in PolicyLayer and add a rule for transitive_reduction: 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 Graph Engine. Nothing to install.
transitive_reduction is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the transitive_reduction 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 transitive_reduction. 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.
transitive_reduction is provided by the Mcp Graph Engine MCP server (utilitydelta/mcp-graph-engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Graph Engine, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 Mcp Graph Engine tools catalogued and risk-classified — across an index of 43,000+ MCP servers.