fulfillment_queue
Print-queue state: status counts (pending/printing/printed/failed) and the 20 most recent jobs (id, order_id, type, status, attempts, error, created_at, printed_at).
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/fulfillment-queue.md
What fulfillment_queue does on Wordpress
AI agents call fulfillment_queue to retrieve information from Wordpress without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why fulfillment_queue is rated Low
Retrieves queue status and job history without creating, modifying, or deleting any data.
From the tool's definition Print-queue state, status counts, most recent jobs; no mutations
Attacks that exploit this kind of access
The rule that runs fulfillment_queue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fulfillment_queue, this is the rule to start with:
fulfillment_queue is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every fulfillment_queue call is checked against it from then on.
Questions about fulfillment_queue
Print-queue state: status counts (pending/printing/printed/failed) and the 20 most recent jobs (id, order_id, type, status, attempts, error, created_at, printed_at). It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.
Register the Wordpress MCP server in PolicyLayer and add a rule for fulfillment_queue: 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 Wordpress. Nothing to install.
fulfillment_queue 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 fulfillment_queue 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 fulfillment_queue. 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.
fulfillment_queue is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wordpress, and thousands of servers like it.
This server
Across the catalogue