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).
This record as markdown: /tools/async23-chrome-devtools-mcp/press-key.md
What press_key does on Chrome Devtools
AI agents invoke press_key to trigger actions in Chrome Devtools. 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 press_key is rated High
Pressing keys triggers browser actions whose effects depend entirely on the arguments and current context — e.g., pressing Enter could submit a form, Delete could remove content, or Ctrl+W could close a tab. This is an external operation with context-dependent side effects, placing it in Execute.
From the tool's definition Press a key or key combination... keyboard shortcuts, navigation keys, or special key combinations
Attacks that exploit this kind of access
The rule that runs press_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every press_key call is checked against it from then on.
Questions about 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). It is categorised as a Execute tool in the Chrome Devtools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
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. Nothing to install.
press_key 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 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.
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.
press_key is provided by the Chrome Devtools MCP server (@async23/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome Devtools, and thousands of servers like it.
Across the catalogue