browserbeam_close · Browserbeam MCP Server MCP

WHAT IT DOES

What browserbeam_close does on Browserbeam MCP Server

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

WHY IT NEEDS A POLICY

Why browserbeam_close needs a policy

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browserbeam_close Rate-limited

browserbeam_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": {
    "browserbeam_close": {
      "limits": [
        {
          "counter": "browserbeam_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 Browserbeam MCP Server, so you can run agents against it safely.

FAQ

Questions about browserbeam_close

What does the browserbeam_close tool do? +

REQUIRED cleanup: Close a browser session and release resources; stops Browserbeam credit consumption. Call this as soon as you are done with the session unless the user explicitly asked to keep it open for immediate follow-up. It is categorised as a Write tool in the Browserbeam 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 browserbeam_close? +

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

What risk level is browserbeam_close? +

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

Can I rate-limit browserbeam_close? +

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

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

browserbeam_close is provided by the Browserbeam MCP Server MCP server (nyku/browserbeam-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.