BM25 keyword search across all indexed symbols — functions, classes, files, routes, etc. Optionally scope to a specific repo or group.
AI agents call search to retrieve information from code-intel 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 and queries indexed code symbols without side effects. It is purely informational, returning search results based on keyword matching. No data is created, modified, deleted, or executed as a result of the search itself.
From the tool's definition Tool performs "BM25 keyword search across all indexed symbols" with optional scoping. The description uses search/query language with no indication of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
BM25 keyword search across all indexed symbols — functions, classes, files, routes, etc. Optionally scope to a specific repo or group. It is categorised as a Read tool in the code-intel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the code-intel MCP Server MCP server in PolicyLayer and add a rule for 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-intel MCP Server. Nothing to install.
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 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 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.
search is provided by the code-intel MCP Server MCP server (vohongtho/code-intel-platform). 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 →