browser_start_session · DevLab MCP Suite MCP: Risk & Policy

WHAT IT DOES

What browser_start_session does on DevLab MCP Suite

AI agents invoke browser_start_session 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_start_session needs a policy

Starting a browser session is an executable action that triggers an external process/environment whose behavior depends on how it is configured and used. While the session itself is for evidence-gathering (neutral purpose), it represents executing and controlling an external system rather than merely reading data.

From the tool's definition Tool description states 'Begin an evidence-gathering session for screenshots and structured reporting' which initiates an external operation (browser session) whose effects depend on arguments and subsequent actions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_start_session Rate-limited

browser_start_session 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_start_session": {
      "limits": [
        {
          "counter": "browser_start_session_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_start_session

What does the browser_start_session tool do? +

Begin an evidence-gathering session for screenshots and structured reporting. 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_start_session? +

Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for browser_start_session: 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_start_session? +

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

Can I rate-limit browser_start_session? +

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

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

browser_start_session 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.