scrappey_browser_action · Scrappey MCP Server MCP

WHAT IT DOES

What scrappey_browser_action does on Scrappey MCP Server

AI agents invoke scrappey_browser_action to trigger actions in Scrappey MCP Server. 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 scrappey_browser_action needs a policy

This tool executes arbitrary JavaScript and browser commands whose effects depend entirely on the arguments provided. While it doesn't directly modify or delete persistent data structures (which would make it Destructive), it can trigger external operations, navigate to malicious sites, interact with web forms, and execute code in a browser environment.

From the tool's definition Tool description explicitly states 'Execute browser automation actions' and 'JavaScript execution', enabling arbitrary code execution in browser context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scrappey_browser_action Rate-limited

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

FAQ

Questions about scrappey_browser_action

What does the scrappey_browser_action tool do? +

Execute browser automation actions in a session. Supports clicking, typing, scrolling, waiting, JavaScript execution, interactive challenge handling, and more. It is categorised as a Execute tool in the Scrappey MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scrappey_browser_action? +

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

What risk level is scrappey_browser_action? +

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

Can I rate-limit scrappey_browser_action? +

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

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

scrappey_browser_action is provided by the Scrappey MCP Server MCP server (pim97/mcp-server-scrappey). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.