reset_emulation · Chromium ARM64 Browser MCP: Risk & Policy

WHAT IT DOES

What reset_emulation does on Chromium ARM64 Browser

AI agents call reset_emulation to permanently remove resources in Chromium ARM64 Browser — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

WHY IT NEEDS A POLICY

Why reset_emulation needs a policy

An AI agent that decides to call reset_emulation doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Chromium ARM64 Browser is gone — there is no undo for destructive operations.

Attacks that exploit this kind of access

Questions about reset_emulation

What does the reset_emulation tool do? +

Reset device emulation back to desktop mode. It is categorised as a Destructive tool in the Chromium ARM64 Browser 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_emulation? +

Register the Chromium ARM64 Browser MCP server in PolicyLayer and add a rule for reset_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 Chromium ARM64 Browser. Nothing to install.

What risk level is reset_emulation? +

reset_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_emulation? +

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

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

reset_emulation is provided by the Chromium ARM64 Browser MCP server (nfodor/mcp-chromium-arm64). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →