Hybrid BM25 + dense-embedding search over all indexed code symbols in the current vault. Returns top-K matches with file paths, line ranges, and relevance score.
AI agents call code.search to retrieve information from Lore Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
code.search is a hybrid search tool (BM25 + dense embeddings) that performs information retrieval over indexed code. It has no side effects: it does not execute code, modify files, delete data, or trigger external operations. The 'Returns' language indicates read-only data retrieval. This is a classic Read category tool with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'Returns top-K matches with file paths, line ranges, and relevance score' — a search operation that retrieves and queries indexed code symbols with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Hybrid BM25 + dense-embedding search over all indexed code symbols in the current vault. Returns top-K matches with file paths, line ranges, and relevance score. It is categorised as a Read tool in the Lore Context MCP Server, which means it retrieves data without modifying state.
Register the Lore Context MCP server in PolicyLayer and add a rule for code.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 Lore Context. Nothing to install.
code.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 code.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 code.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.
code.search is provided by the Lore Context MCP server (Lore-Context/lore-context). 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 →