get_stats

Get statistics about the indexed collection.

SERVERMCP RAG Server SOURCE0xrdan/mcp-rag-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xrdan-mcp-rag-server/get-stats.md

WHAT IT DOES

What get_stats does on MCP RAG Server

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

RISK

Why get_stats is rated Low

This tool queries and returns information (statistics) without side effects. It follows the Read pattern: retrieves or queries data with no modifications. The sibling tools include destructive operations (clear_collection, delete_by_source) and writes (index_document, index_documents_batch), but get_stats is purely informational.

From the tool's definition get_stats retrieves statistics about the indexed collection; the description indicates no data modification, only inspection of collection metadata.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_stats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP RAG Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_stats, this is the rule to start with:

get_stats Allowed

get_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_stats": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP RAG Server, apply this rule, and every get_stats call is checked against it from then on.

FAQ

Questions about get_stats

What does the get_stats tool do? +

Get statistics about the indexed collection. It is categorised as a Read tool in the MCP RAG Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_stats? +

Register the MCP RAG Server 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 RAG Server. 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 RAG Server MCP server (0xrdan/mcp-rag-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP RAG Server, and thousands of servers like it.

This server

All 7 MCP RAG Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →