needle_get_collection_stats
AI agents call needle_get_collection_stats to retrieve information from Needle MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates a 'get' operation that retrieves collection statistics—a read-only query operation. Context from sibling tools like 'needle_list_collections' and 'needle_get_collection_details' (both clearly Read operations) further supports this classification. No evidence of data modification, deletion, execution, or financial operations.
From the tool's definition Tool name 'needle_get_collection_stats' suggests retrieving statistics about a collection. Given the server context manages documents and collections, this operation retrieves information without modifying data.
Attacks that exploit this kind of access
needle_get_collection_stats. It is categorised as a Read tool in the Needle MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Needle MCP Server MCP server in PolicyLayer and add a rule for needle_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 Needle MCP Server. Nothing to install.
needle_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 needle_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 needle_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.
needle_get_collection_stats is provided by the Needle MCP Server MCP server (needle-ai/needle-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 →