browser_type · DevServer MCP: Risk & Policy

WHAT IT DOES

What browser_type does on DevServer MCP

AI agents invoke browser_type to trigger actions in DevServer 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_type needs a policy

The tool name 'browser_type' strongly suggests it types text into browser elements, consistent with Playwright's 'type' action. This is a browser automation Execute action. The description is empty, reducing confidence. Given the sibling tools are all browser automation (click, navigate, screenshot, snapshot), this fits the Execute category as it triggers external browser interactions.

From the tool's definition Tool name 'browser_type' on a server with browser automation tools (browser_click, browser_navigate, browser_snapshot) — part of Playwright-based browser automation suite.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_type Rate-limited

browser_type 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_type": {
      "limits": [
        {
          "counter": "browser_type_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 DevServer MCP, so you can run agents against it safely.

FAQ

Questions about browser_type

What does the browser_type tool do? +

browser_type. It is categorised as a Execute tool in the DevServer 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_type? +

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

What risk level is browser_type? +

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

Can I rate-limit browser_type? +

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

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

browser_type is provided by the DevServer MCP server (uninen/devserver-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.