Scan a directory for all supported source files and report complexity across the codebase. Returns a summary with hotspots.
AI agents call analyze_directory to retrieve information from Time Complexity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool scans source files and generates complexity reports—a pure read operation that retrieves and analyzes data without side effects. The static AST parsing and reporting of metrics constitute information retrieval only. No data is created, modified, deleted, or executed.
From the tool's definition Tool performs static analysis and "report[s] complexity across the codebase" returning a "summary"; no modification, deletion, or execution capabilities are described.
Attacks that exploit this kind of access
Scan a directory for all supported source files and report complexity across the codebase. Returns a summary with hotspots. It is categorised as a Read tool in the Time Complexity MCP Server, which means it retrieves data without modifying state.
Register the Time Complexity MCP server in PolicyLayer and add a rule for analyze_directory: 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 Time Complexity. Nothing to install.
analyze_directory 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_directory 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_directory. 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_directory is provided by the Time Complexity MCP server (luzgan/time-complexity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
analyze_directory is one line of Time Complexity's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →