Reject an official mirror queue entry. This is an async operation that enqueues a background job. This action: 1. Marks the queue entry as rejected 2. Enqueues a background job to process the rejection 3. The entry will not be linked to any MCP server Important: This is an asynchronous operation....
AI agents use reject_official_mirror_queue_item to create or update resources in Playwright Stealth — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Playwright Stealth environment.
This tool modifies state (marks an entry as rejected, enqueues a job) but does so reversibly—the rejection can presumably be undone or the entry re-processed. It lacks the irreversibility of Destructive actions and does not execute arbitrary code. Write is appropriate for state-modifying operations with reversible effects.
From the tool's definition Marks the queue entry as rejected and enqueues a background job to process the rejection. The entry will not be linked to any MCP server.
Documented attack patterns abuse exactly the kind of access reject_official_mirror_queue_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright Stealth, and nothing reaches the server without passing your rules. This is the rule we recommend for reject_official_mirror_queue_item:
{
"version": "1",
"default": "deny",
"tools": {
"reject_official_mirror_queue_item": {
"limits": [
{
"counter": "reject_official_mirror_queue_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reject_official_mirror_queue_item stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Reject an official mirror queue entry. This is an async operation that enqueues a background job. This action: 1. Marks the queue entry as rejected 2. Enqueues a background job to process the rejection 3. The entry will not be linked to any MCP server Important: This is an asynchronous operation. The response indicates the job was enqueued, not that the rejection is complete. Use get_official_mirror_queue_item to poll for completion. Use cases: - Reject submissions that don. It is categorised as a Write tool in the Playwright Stealth MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Playwright Stealth MCP server in PolicyLayer and add a rule for reject_official_mirror_queue_item: 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 Playwright Stealth. Nothing to install.
reject_official_mirror_queue_item 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 reject_official_mirror_queue_item 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 reject_official_mirror_queue_item. 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.
reject_official_mirror_queue_item is provided by the Playwright Stealth MCP server (pulsemcp/mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright Stealth, 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.
68 Playwright Stealth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.