emulate_device · JS Reverse MCP: Risk & Policy

WHAT IT DOES

What emulate_device does on JS Reverse MCP

AI agents invoke emulate_device to trigger actions in JS Reverse MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why emulate_device needs a policy

Device emulation triggers browser operations that execute code paths and modify runtime behavior based on the device profile selected. While it does not create/delete data (not Write/Destructive) and does not move money (not Financial), it actively executes browser state changes whose effects depend on the chosen device argument.

From the tool's definition Tool performs 'emulate a common mobile device profile' in the context of a browser debugging and automation server.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

emulate_device Rate-limited

emulate_device stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "emulate_device": {
      "limits": [
        {
          "counter": "emulate_device_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches JS Reverse MCP, so you can run agents against it safely.

FAQ

Questions about emulate_device

What does the emulate_device tool do? +

Emulate a common mobile device profile. It is categorised as a Execute tool in the JS Reverse MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on emulate_device? +

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

What risk level is emulate_device? +

emulate_device is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit emulate_device? +

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

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

emulate_device is provided by the JS Reverse MCP server (noone-hub/jsreverser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.