Get current queue status and processing statistics
AI agents call get_queue_statistics to retrieve information from Document Parser MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries statistics and status information about the document processing queue. It performs a read-only operation with no side effects, no code execution, and no data modification. The ability to inspect queue state is informational only and poses minimal risk even if invoked by an AI agent. Classified as Read with low severity.
From the tool's definition Tool description states 'Get current queue status and processing statistics' — retrieves queue metrics and status without modifying state or executing operations.
Attacks that exploit this kind of access
Get current queue status and processing statistics. It is categorised as a Read tool in the Document Parser MCP MCP Server, which means it retrieves data without modifying state.
Register the Document Parser MCP server in PolicyLayer and add a rule for get_queue_statistics: 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 Document Parser MCP. Nothing to install.
get_queue_statistics 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_queue_statistics 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_queue_statistics. 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_queue_statistics is provided by the Document Parser MCP server (kgand/document-parser-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 →