browser_press_key

Press a keyboard key (e.g., 'Enter', 'Tab', 'Escape', 'ArrowDown') or a single character. Optional ref focuses an element first — aria-ref token from browser.snapshot ('e7') or a CSS selector.

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp

High RISK CLASS

Category Execute

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/browser-press-key.md

WHAT IT DOES

What browser_press_key does on Dialogbrain

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

Parameter	Type	Required
`key`	string	Yes
`ref`	object	—
`page_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why browser_press_key is rated High

This tool simulates keyboard input in a browser context, triggering UI interactions whose effects depend on what element is focused and what key is pressed. It can submit forms, navigate menus, or trigger arbitrary actions — classic Execute category browser automation. Severity is medium because the blast radius depends on context, but misuse could trigger unintended actions in the browser UI.

From the tool's definition "Press a keyboard key" and "Optional `ref` focuses an element first"

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_press_key safely

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

browser_press_key Rate-limited

browser_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": {
    "browser_press_key": {
      "limits": [
        {
          "counter": "browser_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 Dialogbrain, apply this rule, and every browser_press_key call is checked against it from then on.

FAQ

Questions about browser_press_key

What does the browser_press_key tool do? +

Press a keyboard key (e.g., 'Enter', 'Tab', 'Escape', 'ArrowDown') or a single character. Optional ref focuses an element first — aria-ref token from browser.snapshot ('e7') or a CSS selector. It is categorised as a Execute tool in the Dialogbrain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does browser_press_key accept? +

browser_press_key accepts 3 parameters: key, ref, page_id. Required: key, page_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browser_press_key? +

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

What risk level is browser_press_key? +

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

Can I rate-limit browser_press_key? +

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

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

browser_press_key is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dialogbrain, and thousands of servers like it.

This server

All 225 Dialogbrain tools → High-risk tools on this server →

Across the catalogue

qt_key_press on Qt →browser_click on Percepta MCP Server →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 →