launch_browser · AutoProbe MCP: Risk & Policy

WHAT IT DOES

What launch_browser does on AutoProbeMCP

AI agents invoke launch_browser to trigger actions in AutoProbeMCP. 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 launch_browser needs a policy

launch_browser triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

launch_browser Rate-limited

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

FAQ

Questions about launch_browser

What does the launch_browser tool do? +

Launch a new browser instance (chromium, firefox, or webkit). It is categorised as a Execute tool in the AutoProbeMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on launch_browser? +

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

What risk level is launch_browser? +

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

Can I rate-limit launch_browser? +

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

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

launch_browser is provided by the AutoProbe MCP server (wladastic/autoprobemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.