Analyze a GDScript file and report cyclomatic complexity, function count, line count, etc.
AI agents call analyze_code_complexity to retrieve information from Godot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static code analysis on a GDScript file and returns metrics (cyclomatic complexity, function count, line count). No modifications, deletions, executions, or side effects occur. It is a pure read operation that retrieves and reports analytical data about code structure.
From the tool's definition Tool name 'analyze_code_complexity' and description 'Analyze a GDScript file and report cyclomatic complexity, function count, line count, etc.' indicate static analysis with reporting only.
Attacks that exploit this kind of access
Analyze a GDScript file and report cyclomatic complexity, function count, line count, etc. It is categorised as a Read tool in the Godot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for analyze_code_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 Godot MCP Server. Nothing to install.
analyze_code_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_code_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_code_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_code_complexity is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). 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 →