browser_stop_session · DevLab MCP Suite MCP: Risk & Policy

WHAT IT DOES

What browser_stop_session does on DevLab MCP Suite

AI agents invoke browser_stop_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_stop_session needs a policy

This tool executes an operation that triggers external processes (finalizing a session and generating a report). While not destructive in itself (the session already exists and is being concluded), it performs an active operation that modifies the state of the testing environment.

From the tool's definition Tool description states 'Finalize the evidence session and generate the final report' - this triggers an external operation (session finalization and report generation) whose effects depend on the current state of the automation session.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_stop_session Rate-limited

browser_stop_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_stop_session": {
      "limits": [
        {
          "counter": "browser_stop_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_stop_session

What does the browser_stop_session tool do? +

Finalize the evidence session and generate the final report. 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_stop_session? +

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

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

Can I rate-limit browser_stop_session? +

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

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

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