Low Risk

search_code

Search indexed codebase using natural language queries. Returns semantically relevant code chunks with file paths and line numbers.

How to control search_code ↓

What search_code does on Qdrant MCP Server

AI agents call search_code to retrieve information from Qdrant MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_code needs a policy

This tool performs a semantic search query against an indexed codebase and returns matching code results. It retrieves information without creating, modifying, deleting, or executing code. The operation is read-only with no side effects beyond querying the vector database. Blast radius is minimal—worst case an agent retrieves code it shouldn't see, but no data is altered or actions triggered.

From the tool's definition Tool name 'search_code' and description 'Search indexed codebase using natural language queries. Returns semantically relevant code chunks with file paths and line numbers.' indicate a retrieval operation with no modification or deletion of data.

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

How to control search_code

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_code": {}
  }
}

search_code 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 Qdrant MCP Server — 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_code

What does the search_code tool do? +

Search indexed codebase using natural language queries. Returns semantically relevant code chunks with file paths and line numbers. It is categorised as a Read tool in the Qdrant MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_code? +

Register the Qdrant MCP Server MCP server in PolicyLayer and add a rule for search_code: 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 Qdrant MCP Server. Nothing to install.

What risk level is search_code? +

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

Can I rate-limit search_code? +

Yes. Add a rate_limit block to the search_code 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_code completely? +

Set action: deny in the PolicyLayer policy for search_code. 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_code? +

search_code is provided by the Qdrant MCP Server MCP server (mhalder/qdrant-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Qdrant MCP Server tool call.

Start from Qdrant MCP Server, 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.

20 Qdrant MCP Server 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.