press_key

Press a key or key combination. Use this when other input methods like fill() cannot be used (e.g., keyboard shortcuts, navigation keys, or special key combinations).

SERVERChrome DevTools MCP SOURCEanirbandz/chrome_mcp_devtool

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/anirbandz-chrome-mcp-devtool/press-key.md

WHAT IT DOES

What press_key does on Chrome DevTools MCP

AI agents invoke press_key to trigger actions in Chrome DevTools 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.

RISK

Why press_key is rated High

Pressing keys in a live browser triggers arbitrary side effects depending on what's focused and what key is sent (e.g., Enter could submit a form, Ctrl+W could close a tab, Delete could remove content). This is an action with context-dependent external effects, making it Execute rather than a simple Write or Read.

From the tool's definition "Press a key or key combination" for "keyboard shortcuts, navigation keys, or special key combinations" — triggers browser-level input events whose effects depend entirely on the current page state and key arguments.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs press_key safely

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

press_key Rate-limited

press_key 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": {
    "press_key": {
      "limits": [
        {
          "counter": "press_key_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 Chrome DevTools MCP, apply this rule, and every press_key call is checked against it from then on.

FAQ

Questions about press_key

What does the press_key tool do? +

Press a key or key combination. Use this when other input methods like fill() cannot be used (e.g., keyboard shortcuts, navigation keys, or special key combinations). It is categorised as a Execute tool in the Chrome DevTools 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 press_key? +

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

What risk level is press_key? +

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

Can I rate-limit press_key? +

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

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

press_key is provided by the Chrome DevTools MCP server (anirbandz/chrome_mcp_devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome DevTools, and thousands of servers like it.

This server

All 26 Chrome DevTools tools → High-risk tools on this server →

Across the catalogue

qt_key_press on Qt →send_key_to_window on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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