browser_session_stop · Wmux MCP: Risk & Policy

WHAT IT DOES

What browser_session_stop does on Wmux

AI agents invoke browser_session_stop to trigger actions in Wmux. 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_session_stop needs a policy

Stopping a browser session is an Execute rather than Destructive action because it terminates a process/session without irreversibly deleting persistent data. It has moderate severity because it interrupts ongoing operations and could disrupt workflows, but the effects are not permanent and can be recovered by restarting.

From the tool's definition Tool name 'browser_session_stop' and description 'Stop the current browser session' indicate termination of an active browser automation session.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_session_stop Rate-limited

browser_session_stop 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_session_stop": {
      "limits": [
        {
          "counter": "browser_session_stop_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 Wmux, so you can run agents against it safely.

FAQ

Questions about browser_session_stop

What does the browser_session_stop tool do? +

Stop the current browser session. It is categorised as a Execute tool in the Wmux 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_session_stop? +

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

What risk level is browser_session_stop? +

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

Can I rate-limit browser_session_stop? +

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

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

browser_session_stop is provided by the Wmux MCP server (openwong2kim/wmux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

browser_session_stop is one line of Wmux's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →