Calculate detailed code quality metrics including cyclomatic complexity, maintainability index, and technical debt assessment
AI agents call get_code_metrics to retrieve information from Shell Executor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a code analysis tool that performs static analysis to measure code quality attributes. It retrieves information about existing code and produces metrics/reports as output. There are no side effects, no code execution, no data modification, and no destructive operations.
From the tool's definition The tool 'get_code_metrics' is described as calculating and analyzing code metrics (cyclomatic complexity, maintainability index, technical debt assessment).
Attacks that exploit this kind of access
Calculate detailed code quality metrics including cyclomatic complexity, maintainability index, and technical debt assessment. It is categorised as a Read tool in the Shell Executor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Shell Executor MCP Server MCP server in PolicyLayer and add a rule for get_code_metrics: 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 Shell Executor MCP Server. Nothing to install.
get_code_metrics 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 get_code_metrics 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 get_code_metrics. 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.
get_code_metrics is provided by the Shell Executor MCP Server MCP server (kosiew/zmcp). 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 →