page_emulate_device

Emulate a mobile device profile.

SERVERJshookmcp SOURCE@jshookmcp/jshook

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/page-emulate-device.md

WHAT IT DOES

What page_emulate_device does on Jshookmcp

AI agents invoke page_emulate_device to trigger actions in Jshookmcp. 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.

RISK

Why page_emulate_device is rated High

Modifies browser environment and behavior; effects depend on which device profile is emulated.

From the tool's definition Emulate a mobile device profile; browser automation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs page_emulate_device safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For page_emulate_device, this is the rule to start with:

page_emulate_device Rate-limited

page_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": {
    "page_emulate_device": {
      "limits": [
        {
          "counter": "page_emulate_device_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every page_emulate_device call is checked against it from then on.

FAQ

Questions about page_emulate_device

What does the page_emulate_device tool do? +

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

How do I enforce a policy on page_emulate_device? +

Register the Jshook MCP server in PolicyLayer and add a rule for page_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 Jshookmcp. Nothing to install.

What risk level is page_emulate_device? +

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

Can I rate-limit page_emulate_device? +

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

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

page_emulate_device is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools → High-risk tools on this server →

Across the catalogue

monitor_and_analyze_page on Percepta MCP Server →adb_backup_device on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →