Low Risk

get_stats

Get statistics about the memory collection (total count, status, etc.).

How to control get_stats ↓

What get_stats does on MCP Qdrant Semantic Search

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

Low Risk

Why get_stats needs a policy

This tool only reads and returns metadata and statistics from the Qdrant collection without modifying, deleting, or executing any operations. It has minimal blast radius—worst case, an agent learns statistics about stored memories, which poses no security or safety risk. Classification as Read is appropriate.

From the tool's definition Tool retrieves statistics ('Get statistics about the memory collection (total count, status, etc.)') with no modification or deletion of data. Purely observational/queryable operation.

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

How to control get_stats

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

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

get_stats 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 MCP Qdrant Semantic Search — 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_stats

What does the get_stats tool do? +

Get statistics about the memory collection (total count, status, etc.). It is categorised as a Read tool in the MCP Qdrant Semantic Search MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_stats? +

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

What risk level is get_stats? +

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

Can I rate-limit get_stats? +

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

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

get_stats is provided by the MCP Qdrant Semantic Search MCP server (muhammedehab35/mcp-qdrant-semantic-search). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Qdrant Semantic Search tool call.

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

7 MCP Qdrant Semantic Search 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.