browser_automation · VibeServe MCP: Risk & Policy

WHAT IT DOES

What browser_automation does on VibeServe

AI agents invoke browser_automation to trigger actions in VibeServe. 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_automation needs a policy

This tool executes browser actions via Playwright, which can perform arbitrary web interactions including form submissions, clicks, navigation, and data exfiltration. While each call uses an isolated incognito context, the tool can trigger external operations (logins, purchases, form posts, API calls) whose effects depend entirely on the arguments provided.

From the tool's definition 'Control a headless browser using a Playwright-based DSL. Use for automation, scraping, or web interactions.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_automation Rate-limited

browser_automation 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_automation": {
      "limits": [
        {
          "counter": "browser_automation_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 VibeServe, so you can run agents against it safely.

FAQ

Questions about browser_automation

What does the browser_automation tool do? +

Control a headless browser using a Playwright-based DSL. Use for automation, scraping, or web interactions. Isolated incognito context is created per call. It is categorised as a Execute tool in the VibeServe 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_automation? +

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

What risk level is browser_automation? +

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

Can I rate-limit browser_automation? +

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

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

browser_automation is provided by the VibeServe MCP server (ncsound919/vibeserve). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.