Get metrics about job and IO queue health.
AI agents call get_queue_stats to retrieve information from Workflows without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries system metrics and health statistics without creating, modifying, executing, or destroying any data or workflows. It is purely informational, similar to a status check or monitoring dashboard query. No blast radius from misuse beyond information disclosure.
From the tool's definition Tool name 'get_queue_stats' and description 'Get metrics about job and IO queue health' indicate a retrieval/query operation. The verb 'Get' and absence of any modification language confirm this is read-only. Returns monitoring data with no side effects.
Documented attack patterns abuse exactly the kind of access get_queue_stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Workflows, and nothing reaches the server without passing your rules. This is the rule we recommend for get_queue_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_queue_stats": {}
}
}get_queue_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get metrics about job and IO queue health. It is categorised as a Read tool in the Workflows MCP Server, which means it retrieves data without modifying state.
Register the Workflows MCP server in PolicyLayer and add a rule for get_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 Workflows. Nothing to install.
get_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 get_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 get_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.
get_queue_stats is provided by the Workflows MCP server (qtsone/workflows-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Workflows, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Workflows tools catalogued and risk-classified — across an index of 43,000+ MCP servers.