Combined semantic search across code and git history for a single repository.
AI agents call contextual_search 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.
This tool performs semantic search operations across code and git history, returning results without modifying, deleting, or executing any external operations. It is a pure read operation that retrieves and queries existing data. No destructive, write, execute, or financial operations are possible with this tool.
From the tool's definition Tool name 'contextual_search' and description 'Combined semantic search across code and git history' indicate data retrieval only. The words 'search' and 'for a single repository' confirm query-based functionality with no side effects.
Documented attack patterns abuse exactly the kind of access contextual_search gives an agent:
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 contextual_search:
{
"version": "1",
"default": "deny",
"tools": {
"contextual_search": {}
}
} contextual_search 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.
Combined semantic search across code and git history for a single repository. It is categorised as a Read tool in the Qdrant MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qdrant MCP Server MCP server in PolicyLayer and add a rule for contextual_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 Qdrant MCP Server. Nothing to install.
contextual_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 contextual_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 contextual_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.
contextual_search 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.
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.