queue_stats

Get Queue 2.0 statistics including auto-approval rates, review times, and cleanup metrics.

SERVERElementify MCP SOURCEvamerli/elementify-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vamerli-elementify-mcp/queue-stats.md

WHAT IT DOES

What queue_stats does on Elementify MCP

AI agents call queue_stats to retrieve information from Elementify MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why queue_stats is rated Low

This tool retrieves and queries statistical data about a queue system without performing any side effects. It falls squarely into the Read category as it gathers information for monitoring purposes. The severity is low because accessing queue statistics poses minimal risk even if misused by an AI agent, as no data is modified, deleted, or financial operations are triggered.

From the tool's definition Tool name 'queue_stats' and description 'Get Queue 2.0 statistics' — uses verb 'Get' indicating data retrieval only.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs queue_stats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Elementify MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For queue_stats, this is the rule to start with:

queue_stats Allowed

queue_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "queue_stats": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Elementify MCP, apply this rule, and every queue_stats call is checked against it from then on.

FAQ

Questions about queue_stats

What does the queue_stats tool do? +

Get Queue 2.0 statistics including auto-approval rates, review times, and cleanup metrics. It is categorised as a Read tool in the Elementify MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on queue_stats? +

Register the Elementify MCP server in PolicyLayer and add a rule for 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 Elementify MCP. Nothing to install.

What risk level is queue_stats? +

queue_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit queue_stats? +

Yes. Add a rate_limit block to the 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.

How do I block queue_stats completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides queue_stats? +

queue_stats is provided by the Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Elementify, and thousands of servers like it.

This server

All 269 Elementify tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →