AI agents call find_complex_files to retrieve information from Codescan 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 code metrics from files without side effects. It examines file characteristics (length, nesting, complexity) and reports findings. No data is created, modified, deleted, or executed. The severity is low because misuse produces only informational output with no capability to harm systems or data.
From the tool's definition Tool performs static analysis scanning: 'Find files that are unusually long, deeply nested, or have high complexity indicators'.
Attacks that exploit this kind of access
Find files that are unusually long, deeply nested, or have high complexity indicators. It is categorised as a Read tool in the Codescan MCP Server, which means it retrieves data without modifying state.
Register the Codescan MCP server in PolicyLayer and add a rule for find_complex_files: 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 Codescan. Nothing to install.
find_complex_files 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_complex_files 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_complex_files. 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_complex_files is provided by the Codescan MCP server (yifanyifan897645/codescan-mcp). 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 →