get_collection_stats
AI agents call get_collection_stats to retrieve information from FastMCP Document Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the tool name and context strongly indicate this is a query operation that retrieves or aggregates statistics about stored documents. No side effects are implied. Confidence is slightly lowered due to the missing description, but the 'get_' prefix and 'stats' suffix are reliable indicators of read-only retrieval.
From the tool's definition Tool name 'get_collection_stats' indicates retrieval of statistical information about a collection. Sibling tools on the server include read operations (get_document, list_documents, search_documents, analyze_document) and write/destructive operations…
Attacks that exploit this kind of access
get_collection_stats. It is categorised as a Read tool in the FastMCP Document Analyzer MCP Server, which means it retrieves data without modifying state.
Register the FastMCP Document Analyzer MCP server in PolicyLayer and add a rule for get_collection_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 FastMCP Document Analyzer. Nothing to install.
get_collection_stats 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 get_collection_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.
Set action: deny in the PolicyLayer policy for get_collection_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.
get_collection_stats is provided by the FastMCP Document Analyzer MCP server (tathagat017/document-analyser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →