countDocuments
AI agents call countDocuments to retrieve information from Amazon MQ 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 'countDocuments' semantically implies counting or querying existing documents without side effects. This is consistent with Read category operations. Severity is low because counting operations have minimal blast radius.
From the tool's definition Tool name 'countDocuments' indicates a read-only query operation that counts documents without modifying data. No description provided to confirm, but naming convention strongly suggests retrieval/aggregation.
Attacks that exploit this kind of access
countDocuments. It is categorised as a Read tool in the Amazon MQ MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for countDocuments: 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 Amazon MQ MCP Server. Nothing to install.
countDocuments 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 countDocuments 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 countDocuments. 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.
countDocuments is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.