Find recurring code patterns across functions
AI agents call find_code_patterns to retrieve information from FDEP 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 by searching for and returning information about code patterns. It has no side effects on the codebase, does not execute code, does not modify data, and does not delete anything. It is purely an informational/query-based tool that fits the 'Read' category. The low severity reflects that misuse would only expose code analysis insights without capability for harm.
From the tool's definition Tool name 'find_code_patterns' and description 'Find recurring code patterns across functions' describe a query/analysis operation that retrieves and identifies patterns within existing code without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Find recurring code patterns across functions. It is categorised as a Read tool in the FDEP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FDEP MCP Server MCP server in PolicyLayer and add a rule for find_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 FDEP MCP Server. Nothing to install.
find_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 find_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 find_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.
find_code_patterns is provided by the FDEP MCP Server MCP server (juspay/fdep-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 →