Find similar code patterns (searches local first, then remote)
AI agents call find_similar_patterns to retrieve information from ChromaDB Local 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 pattern matching and searching across code, returning similar results without creating, modifying, or deleting any data. It has no side effects beyond information retrieval, making it a Read operation with low severity risk. The low blast radius reflects that misuse would only expose information already stored in the system.
From the tool's definition Tool name 'find_similar_patterns' and description indicate it searches and retrieves code patterns without modifying data. The phrase 'searches local first, then remote' confirms a query/retrieval operation.
Attacks that exploit this kind of access
Find similar code patterns (searches local first, then remote). It is categorised as a Read tool in the ChromaDB Local MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ChromaDB Local MCP Server MCP server in PolicyLayer and add a rule for find_similar_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 ChromaDB Local MCP Server. Nothing to install.
find_similar_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_similar_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_similar_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_similar_patterns is provided by the ChromaDB Local MCP Server MCP server (vespo92/chromadblocal-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 →