Low Risk

federated_search

Search across multiple indexed repositories simultaneously.

How to control federated_search ↓

What federated_search does on Qdrant MCP Server

AI agents call federated_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.

Low Risk

Why federated_search needs a policy

Federated search queries existing indexed data across multiple repositories. It retrieves and returns results but does not create, modify, delete, or execute external operations. This aligns with the 'Read' category for data retrieval with no side effects.

From the tool's definition The tool is named 'federated_search' and described as 'Search across multiple indexed repositories simultaneously.' The verb 'search' and the context of the Qdrant server (which 'Supports natural language queries') indicate a read-only operation that…

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

How to control federated_search

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 federated_search:

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

federated_search 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 federated_search

What does the federated_search tool do? +

Search across multiple indexed repositories simultaneously. 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 federated_search? +

Register the Qdrant MCP Server MCP server in PolicyLayer and add a rule for federated_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.

What risk level is federated_search? +

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

Can I rate-limit federated_search? +

Yes. Add a rate_limit block to the federated_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.

How do I block federated_search completely? +

Set action: deny in the PolicyLayer policy for federated_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.

What MCP server provides federated_search? +

federated_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.

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.