browser_create · Scrapeless MCP: Risk & Policy

WHAT IT DOES

What browser_create does on Scrapeless

AI agents invoke browser_create to trigger actions in Scrapeless. 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_create needs a policy

This tool launches or reattaches to a cloud browser session, which is an external operation that establishes a stateful execution environment. It falls under Execute because it triggers external infrastructure (cloud browser) and updates active session state. The blast radius is high since a misused session can be used for scraping, credential theft, or further browser actions via sibling tools.

From the tool's definition 'Create or reuse a cloud browser session' and 'Updates the active session' — initiates an external cloud browser process with ongoing state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_create Rate-limited

browser_create 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_create": {
      "limits": [
        {
          "counter": "browser_create_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 Scrapeless, so you can run agents against it safely.

FAQ

Questions about browser_create

What does the browser_create tool do? +

Create or reuse a cloud browser session using Scrapeless. Updates the active session. It is categorised as a Execute tool in the Scrapeless 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_create? +

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

What risk level is browser_create? +

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

Can I rate-limit browser_create? +

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

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

browser_create is provided by the Scrapeless MCP server (scrapeless-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.