Semantic search using ChromaDB.
AI agents call semantic_search to retrieve information from Code Intelligence 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 a read-only information retrieval operation using ChromaDB (a vector database). Semantic search queries embeddings to find relevant code sections but does not create, modify, execute, or delete anything. The operation has no side effects on the codebase. It falls squarely into the Read category—a safe, informational tool for code exploration.
From the tool's definition semantic_search using ChromaDB retrieves and queries code embeddings without modifying or executing code. The tool description indicates it performs search operations over existing data structures.
Attacks that exploit this kind of access
Semantic search using ChromaDB. It is categorised as a Read tool in the Code Intelligence MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Code Intelligence MCP Server MCP server in PolicyLayer and add a rule for semantic_search: 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 Code Intelligence MCP Server. Nothing to install.
semantic_search 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 semantic_search 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 semantic_search. 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.
semantic_search is provided by the Code Intelligence MCP Server MCP server (tech-spoke/llm-helper). 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 →