AI agents invoke mobile_mode to trigger actions in Chrome MCP Docker. 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.
This tool modifies the browser's viewport configuration by toggling mobile emulation mode. It triggers an external browser operation (changing device emulation settings via DevTools Protocol) that affects subsequent browser behavior.
From the tool's definition Toggles mobile viewport (iPhone X dimensions)
Documented attack patterns abuse exactly the kind of access mobile_mode gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chrome MCP Docker, and nothing reaches the server without passing your rules. This is the rule we recommend for mobile_mode:
{
"version": "1",
"default": "deny",
"tools": {
"mobile_mode": {
"limits": [
{
"counter": "mobile_mode_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} mobile_mode 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.
Free to start. No card required.
Toggles mobile viewport (iPhone X dimensions). It is categorised as a Execute tool in the Chrome MCP Docker MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Chrome MCP Docker MCP server in PolicyLayer and add a rule for mobile_mode: 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 Chrome MCP Docker. Nothing to install.
mobile_mode is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mobile_mode 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 mobile_mode. 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.
mobile_mode is provided by the Chrome MCP Docker MCP server (null-runner/chrome-mcp-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Chrome MCP Docker, 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.
10 Chrome MCP Docker tools catalogued and risk-classified — across an index of 43,000+ MCP servers.