Enqueue a write operation for delayed execution. Returns immediately with a queue ID. The action will be executed after a random delay within the specified range. Use queue_status to check progress.
AI agents use queue_action to create or update resources in Reddirect — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reddirect environment.
This tool enqueues write operations (creates or modifies data) for delayed execution rather than immediate application. While it modifies state, the operations are reversible (posts can be edited or deleted, votes can be changed). The delayed execution mechanism and queue abstraction add operational complexity but do not elevate it to Destructive (which would be irreversible).
From the tool's definition Tool description explicitly states 'Enqueue a write operation for delayed execution' and is part of a server that includes tools like 'create_post', 'delete_content', and 'edit_content'. The write operation capability is clearly indicated.
Attacks that exploit this kind of access
Enqueue a write operation for delayed execution. Returns immediately with a queue ID. The action will be executed after a random delay within the specified range. Use queue_status to check progress. It is categorised as a Write tool in the Reddirect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reddirect MCP server in PolicyLayer and add a rule for queue_action: 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 Reddirect. Nothing to install.
queue_action is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the queue_action 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 queue_action. 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.
queue_action is provided by the Reddirect MCP server (jeebus87/reddirect). 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 →