Search the indexed codebase. Default compact mode returns at most 6 ranked results with
AI agents call search_codebase to retrieve information from Codebase Context 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 codebase information without side effects. It matches the Read category definition of 'retrieves or queries data; no side effects (search, list, get, fetch)'. The severity is low because the blast radius of misuse is limited to information disclosure of existing codebase content, which is typically less sensitive than code execution or data destruction risks.
From the tool's definition Tool name is 'search_codebase' and description states it 'Search[es] the indexed codebase' with results returned. No modification, deletion, or execution capability is mentioned. The tool purely retrieves indexed data from the codebase.
Documented attack patterns abuse exactly the kind of access search_codebase gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Codebase Context, and nothing reaches the server without passing your rules. This is the rule we recommend for search_codebase:
{
"version": "1",
"default": "deny",
"tools": {
"search_codebase": {}
}
} search_codebase is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search the indexed codebase. Default compact mode returns at most 6 ranked results with. It is categorised as a Read tool in the Codebase Context MCP Server, which means it retrieves data without modifying state.
Register the Codebase Context MCP server in PolicyLayer and add a rule for search_codebase: 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 Codebase Context. Nothing to install.
search_codebase 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_codebase 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_codebase. 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_codebase is provided by the Codebase Context MCP server (patricksys/codebase-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Codebase Context tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Codebase Context tools catalogued and risk-classified — across an index of 42,500+ MCP servers.