Approve an official mirror queue entry without modifying the linked MCP server. This is a synchronous operation. This action: 1. Marks the queue entry as approved 2. Does NOT update the linked MCP server with mirror data 3. Requires the queue entry to already be linked to a server Use this when: ...
AI agents use approve_mirror_no_modify 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 creates or modifies data (the approval status of a queue entry) in a reversible manner. It does not execute arbitrary code, delete data irreversibly, or move money. While it affects system state, the change is not inherently destructive—approval status can typically be reverted or modified.
From the tool's definition Tool description states it 'Marks the queue entry as approved' and performs a state change operation on a queue entry without being destructive or undoable in the immediate sense. The synchronous operation modifies queue entry status.
Documented attack patterns abuse exactly the kind of access approve_mirror_no_modify 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 approve_mirror_no_modify:
{
"version": "1",
"default": "deny",
"tools": {
"approve_mirror_no_modify": {
"limits": [
{
"counter": "approve_mirror_no_modify_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}approve_mirror_no_modify 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.
Approve an official mirror queue entry without modifying the linked MCP server. This is a synchronous operation. This action: 1. Marks the queue entry as approved 2. Does NOT update the linked MCP server with mirror data 3. Requires the queue entry to already be linked to a server Use this when: - The queue entry shows an update (pending_update) but you want to acknowledge it without applying changes - The existing server data is correct and doesn. 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 approve_mirror_no_modify: 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.
approve_mirror_no_modify 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 approve_mirror_no_modify 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 approve_mirror_no_modify. 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.
approve_mirror_no_modify 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.