Get the current background-queue stats: pending/running/done/failed counts, throughput, lag.\n\n
AI agents call wafle_system_queue_stats to retrieve information from wafle MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves monitoring/observability data about system queue performance. It has no side effects, does not modify data, execute commands, delete records, or commit financial transactions. It is purely informational, fitting the Read category at low severity.
From the tool's definition Tool description states 'Get the current background-queue stats: pending/running/done/failed counts, throughput, lag.' The verb 'Get' and the focus on retrieving queue statistics with no mention of modifications, deletions, or side effects indicates a…
Attacks that exploit this kind of access
Get the current background-queue stats: pending/running/done/failed counts, throughput, lag.\n\n. It is categorised as a Read tool in the wafle MCP server MCP Server, which means it retrieves data without modifying state.
Register the wafle MCP server MCP server in PolicyLayer and add a rule for wafle_system_queue_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 wafle MCP server. Nothing to install.
wafle_system_queue_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 wafle_system_queue_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 wafle_system_queue_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.
wafle_system_queue_stats is provided by the wafle MCP server MCP server (the33warehouse-tech/wafle-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 →