Low Risk

search_codebase

Search through indexed codebases

How to control search_codebase ↓

What search_codebase does on Claude Context Local

AI agents call search_codebase to retrieve information from Claude Context Local without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_codebase needs a policy

This tool performs a read-only search operation against pre-indexed codebases. It retrieves matching results from a local PostgreSQL index but does not create, modify, delete, or execute any code. The operation is passive data retrieval with no side effects, making it a Read category risk.

From the tool's definition Tool name 'search_codebase' and description 'Search through indexed codebases' indicate a query operation that retrieves data without modification or execution.

Documented attack patterns abuse exactly the kind of access search_codebase gives an agent:

How to control search_codebase

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Context Local, and nothing reaches the server without passing your rules. This is the rule we recommend for search_codebase:

policy.json
{
  "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.

  1. Create a free account and register Claude Context Local — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_codebase

What does the search_codebase tool do? +

Search through indexed codebases. It is categorised as a Read tool in the Claude Context Local MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_codebase? +

Register the Claude Context Local 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 Claude Context Local. Nothing to install.

What risk level is search_codebase? +

search_codebase is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_codebase? +

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.

How do I block search_codebase completely? +

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.

What MCP server provides search_codebase? +

search_codebase is provided by the Claude Context Local MCP server (mikeo-ai/claude-context-local). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Context Local tool call.

Start from Claude Context Local, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

9 Claude Context Local tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.