Detect design patterns and anti-patterns in code
AI agents call detect_code_patterns 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 tool analyzes code to identify patterns without executing commands, modifying files, or triggering external operations. It is a read-only inspection capability, analogous to static code analysis. Despite being on a 'Shell Executor' server, the tool itself performs no shell execution or side effects. Severity is low because misuse yields only informational output that cannot harm systems or data.
From the tool's definition Tool description states it 'Detect[s] design patterns and anti-patterns in code' — a purely analytical operation with no modification, execution, or deletion. The verb 'detect' indicates analysis/inspection only.
Attacks that exploit this kind of access
Detect design patterns and anti-patterns in code. 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 detect_code_patterns: 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.
detect_code_patterns 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 detect_code_patterns 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 detect_code_patterns. 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.
detect_code_patterns 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 →