Critical Risk →

reset_device_emulation

Remove all device emulation overrides and restore the original

Part of the Safari DevTools MCP server.

reset_device_emulation can permanently delete data in Safari DevTools MCP, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SAFARI DEVTOOLS MCP →

Free to start. No card required.

AI agents may call reset_device_emulation to permanently remove or destroy resources in Safari DevTools MCP. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call reset_device_emulation in a loop, permanently destroying resources in Safari DevTools MCP. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "reset_device_emulation"
  ]
}

See the full Safari DevTools MCP policy for all 53 tools.

Get this rule live on your own Safari DevTools MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SAFARI DEVTOOLS MCP →

View all 53 tools →

These attack patterns abuse exactly the kind of access reset_device_emulation gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so reset_device_emulation only ever does what you allow.

SECURE SAFARI DEVTOOLS MCP →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the reset_device_emulation tool do? +

Remove all device emulation overrides and restore the original. It is categorised as a Destructive tool in the Safari DevTools MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on reset_device_emulation? +

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

What risk level is reset_device_emulation? +

reset_device_emulation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit reset_device_emulation? +

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

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

reset_device_emulation is provided by the Safari DevTools MCP server (safari-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Safari DevTools MCP tool call.

Deterministic rules across all 53 Safari DevTools MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.