browser_press · MCP: Risk & Policy

WHAT IT DOES

What browser_press does on Mcp

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

WHY IT NEEDS A POLICY

Why browser_press needs a policy

This tool triggers browser actions by simulating keyboard input on a page or focused element. It performs external operations whose effects depend on the arguments (which key is pressed and where), which could trigger form submissions, navigation, or other page interactions. This falls under Execute as it drives browser behavior.

From the tool's definition Press a keyboard key on the page or a focused selector

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_press Rate-limited

browser_press 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": {
      "limits": [
        {
          "counter": "browser_press_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 Mcp, so you can run agents against it safely.

FAQ

Questions about browser_press

What does the browser_press tool do? +

Press a keyboard key on the page or a focused selector. It is categorised as a Execute tool in the 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 browser_press? +

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

What risk level is browser_press? +

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

Can I rate-limit browser_press? +

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

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

browser_press is provided by the MCP server (victormyschik/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.