Low Risk

get_collection_info

Get detailed information about a collection including vector size, point count, and distance metric.

How to control get_collection_info ↓

What get_collection_info does on Qdrant MCP Server

AI agents call get_collection_info 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 get_collection_info needs a policy

This tool queries and returns metadata about a collection without modifying, deleting, or executing operations. It is a straightforward read operation on database schema information.

From the tool's definition Tool name is 'get_collection_info' and description states it retrieves 'detailed information about a collection including vector size, point count, and distance metric' — purely data retrieval with no side effects.

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

How to control get_collection_info

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

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

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

What does the get_collection_info tool do? +

Get detailed information about a collection including vector size, point count, and distance metric. 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 get_collection_info? +

Register the Qdrant MCP Server MCP server in PolicyLayer and add a rule for get_collection_info: 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 get_collection_info? +

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

Can I rate-limit get_collection_info? +

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

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

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