Analyzes circular dependencies (cycles) in the codebase. Detects files that depend on each other in a circular way, which violates good architecture principles. Critical when Domain layer is involved.
AI agents call analyze_cycles to retrieve information from MMI Architecture Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and evaluates the codebase to identify architectural issues (circular dependencies) without modifying, executing, or destructively altering any data or code. It is purely an analysis/reporting function that retrieves structural information about the project. The low severity reflects that misuse would at worst surface incorrect analysis, with no side effects on the codebase itself.
From the tool's definition The tool 'analyzes circular dependencies' and 'detects files that depend on each other', performing static analysis of code structure. The description contains only analysis/detection verbs with no mention of modifying, executing, or deleting code.
Attacks that exploit this kind of access
Analyzes circular dependencies (cycles) in the codebase. Detects files that depend on each other in a circular way, which violates good architecture principles. Critical when Domain layer is involved. It is categorised as a Read tool in the MMI Architecture Analyzer MCP Server, which means it retrieves data without modifying state.
Register the MMI Architecture Analyzer MCP server in PolicyLayer and add a rule for analyze_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 MMI Architecture Analyzer. Nothing to install.
analyze_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 analyze_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 analyze_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.
analyze_cycles is provided by the MMI Architecture Analyzer MCP server (lady-logic/mmi-analyzer). 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 →