browser_press_key · DevLab MCP Suite MCP: Risk & Policy

WHAT IT DOES

What browser_press_key does on DevLab MCP Suite

AI agents invoke browser_press_key to trigger actions in DevLab MCP Suite. 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 IT NEEDS A POLICY

Why browser_press_key needs a policy

This tool executes a browser action by injecting keyboard input into a live web page. While a single keypress seems benign, misuse could trigger form submissions, confirmations, deletions, or navigation — making it an Execute-category tool with medium severity.

From the tool's definition "Send a keyboard key press to the page" — triggers an external browser action (keyboard input) on a live page

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DevLab MCP Suite, so you can run agents against it safely.

FAQ

Questions about browser_press_key

What does the browser_press_key tool do? +

Send a keyboard key press to the page. Use Playwright key names (Enter, Space, ArrowUp, KeyA, etc.). It is categorised as a Execute tool in the DevLab MCP Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_press_key? +

Register the DevLab MCP Suite 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 DevLab MCP Suite. 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 DevLab MCP Suite MCP server (tanguito86/devlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.