Analyze code complexity. Args: project: Project name file_path: Path to the file Returns: Complexity metrics
AI agents call analyze_complexity to retrieve information from Tree Sitter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes static properties of code (complexity metrics) without executing it, modifying project state, or triggering external operations. It is a read-only analytical capability. Severity is low because misuse would at worst expose internal code structure metrics, not cause operational harm.
From the tool's definition Tool name 'analyze_complexity' and description 'Analyze code complexity' with arguments limited to project name and file path, returning 'Complexity metrics'. The verb 'analyze' indicates inspection/querying without modification or execution.
Documented attack patterns abuse exactly the kind of access analyze_complexity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tree Sitter, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_complexity:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_complexity": {}
}
}analyze_complexity 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.
Analyze code complexity. Args: project: Project name file_path: Path to the file Returns: Complexity metrics. It is categorised as a Read tool in the Tree Sitter MCP Server, which means it retrieves data without modifying state.
Register the Tree Sitter MCP server in PolicyLayer and add a rule for analyze_complexity: 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 Tree Sitter. Nothing to install.
analyze_complexity 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_complexity 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_complexity. 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_complexity is provided by the Tree Sitter MCP server (wrale/mcp-server-tree-sitter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 Tree Sitter tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
26 Tree Sitter tools catalogued and risk-classified — across an index of 42,500+ MCP servers.