AI agents call find_cycles to retrieve information from Mcp Graph Engine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs cycle detection, a standard graph analysis algorithm that retrieves and analyzes existing graph properties. It returns information about circular relationships but does not create, modify, delete, or execute external operations. The operation is read-only with no capability to alter the graph state or trigger external systems.
From the tool's definition Tool name 'find_cycles' and description 'Detect cycles (circular dependencies) in the graph' indicate a query/analysis operation that examines graph structure without modifying or deleting data. No side effects or irreversible actions are described.
Documented attack patterns abuse exactly the kind of access find_cycles 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 find_cycles:
{
"version": "1",
"default": "deny",
"tools": {
"find_cycles": {}
}
}find_cycles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Detect cycles (circular dependencies) in the graph. It is categorised as a Read tool in the Mcp Graph Engine MCP Server, which means it retrieves data without modifying state.
Register the Mcp Graph Engine MCP server in PolicyLayer and add a rule for find_cycles: 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.
find_cycles 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 find_cycles 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 find_cycles. 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.
find_cycles 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.