分析源代码复杂度并返回结果
AI agents call analyze_code_complexity to retrieve information from Code2Flow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads source code and computes complexity metrics, producing informational output only. There are no side effects, no data modification, no code execution, and no destructive operations. It fits the Read category—a query operation that retrieves analytical insights from existing code without changing state.
From the tool's definition Tool performs code analysis and returns complexity metrics ("analyze_code_complexity", "returns results"). The description indicates data retrieval and metric calculation without modification, creation, or execution of external operations.
Attacks that exploit this kind of access
分析源代码复杂度并返回结果. It is categorised as a Read tool in the Code2Flow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Code2Flow 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 Code2Flow 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 Code2Flow MCP Server MCP server (kursk-ye/code2flow-mcp-server). 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 →