multi_browserbase_stagehand_session_close

Server Browserbase MCP Server ronsdad/mcp-server-browserbase

Category Write

Risk class Medium

Parameters 00 required

WHAT IT DOES

What multi_browserbase_stagehand_session_close does on Browserbase MCP Server

AI agents use multi_browserbase_stagehand_session_close to create or update resources in Browserbase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Browserbase MCP Server environment.

WHY IT NEEDS A POLICY

Why multi_browserbase_stagehand_session_close needs a policy

An AI agent can call multi_browserbase_stagehand_session_close faster than any human can review — one bad instruction and it creates or modifies resources in Browserbase MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

multi_browserbase_stagehand_session_close Rate-limited

multi_browserbase_stagehand_session_close stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "multi_browserbase_stagehand_session_close": {
      "limits": [
        {
          "counter": "multi_browserbase_stagehand_session_close_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Browserbase MCP Server, so you can run agents against it safely.

FAQ

Questions about multi_browserbase_stagehand_session_close

What does the multi_browserbase_stagehand_session_close tool do? +

Cleanup parallel session for multi-session workflows. Properly terminates a browser session, ends the Browserbase session, and frees cloud resources. Always use this when finished with a session to avoid resource waste and billing charges. Critical for responsible multi-session automation - each unclosed session continues consuming resources!. It is categorised as a Write tool in the Browserbase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on multi_browserbase_stagehand_session_close? +

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

What risk level is multi_browserbase_stagehand_session_close? +

multi_browserbase_stagehand_session_close is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit multi_browserbase_stagehand_session_close? +

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

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

multi_browserbase_stagehand_session_close is provided by the Browserbase MCP Server MCP server (ronsdad/mcp-server-browserbase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.