Detect circular import chains or mutual-recursion call cycles in the codebase. Returns each cycle as an ordered list of file paths or symbol names.
AI agents call find_cycles to retrieve information from GraphHub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis of the codebase to identify cycles, purely retrieving information about code structure without creating, modifying, deleting, or executing any code. It is a read-only operation with no side effects, making it a 'Read' category tool with low severity.
From the tool's definition Tool 'find_cycles' analyzes and detects circular import chains and mutual-recursion patterns, returning results as ordered lists. The verb 'detect' and the output format indicate data retrieval and analysis with no modification or side effects.
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 GraphHub, 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 circular import chains or mutual-recursion call cycles in the codebase. Returns each cycle as an ordered list of file paths or symbol names. It is categorised as a Read tool in the GraphHub MCP Server, which means it retrieves data without modifying state.
Register the GraphHub 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 GraphHub. 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 GraphHub MCP server (slnquangtran/graph-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GraphHub, 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.
32 GraphHub tools catalogued and risk-classified — across an index of 43,000+ MCP servers.