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).
AI agents invoke press_key to trigger actions in Opera 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.
This tool simulates keyboard input in a browser, which can trigger arbitrary browser actions depending on which keys are pressed. While it's a form of browser interaction, pressing keys can execute commands, submit forms, navigate pages, or trigger shortcuts — making it an Execute-category tool. Misuse could trigger unintended actions in a web application.
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
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 Opera DevTools MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Opera 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 Opera DevTools MCP. 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 Opera DevTools MCP server (operasoftware/opera-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →