Search for relevant context in ChromaDB (automatically routes to local or remote)
AI agents call search_context 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 retrieves or queries data from ChromaDB vector storage without creating, modifying, deleting, or executing side effects. It is a passive search operation that returns matching context/results. The automatic routing mentioned is internal orchestration and does not change the read-only nature of the operation.
From the tool's definition Tool name 'search_context' and description 'Search for relevant context in ChromaDB' indicates a query/retrieval operation with no data modification capability. The verb 'search' and 'routes to' are characteristic of read-only operations.
Attacks that exploit this kind of access
Search for relevant context in ChromaDB (automatically routes to local or 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 search_context: 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.
search_context 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 search_context 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 search_context. 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.
search_context 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 →