Count documents in a collection matching a query
AI agents call count_documents to retrieve information from Google Services MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a collection to return a count of matching documents. It retrieves data without creating, modifying, deleting, or executing external operations. The operation is purely informational and has no side effects on the underlying data.
From the tool's definition Tool name is 'count_documents' and description states it 'Count documents in a collection matching a query'. The verb 'count' and absence of modification language indicate a read-only operation that retrieves aggregate information without side effects.
Attacks that exploit this kind of access
Count documents in a collection matching a query. It is categorised as a Read tool in the Google Services MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Services MCP Server MCP server in PolicyLayer and add a rule for count_documents: 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 Google Services MCP Server. Nothing to install.
count_documents 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 count_documents 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 count_documents. 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.
count_documents is provided by the Google Services MCP Server MCP server (t4nm4ymittal/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 →