// SCAN REPORT

Scrappey MCP Server

7 tools. 4 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 1 Jul 2026

4 can modify or destroy data

3 read-only

7 tools total

Community server · catalogue entry verified 01/07/2026

How to control Scrappey MCP Server ↓

TOOL MAP

What Scrappey MCP Server exposes to your agents

Read (3) Write / Execute (3) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Scrappey MCP Server tools

Destructive · Medium scrappey_destroy_session This tool irreversibly terminates a browser session, preventing further use of that session. Execute · High scrappey_browser_action This tool executes arbitrary JavaScript and browser commands whose effects depend entirely on the arguments provided. Execute · Medium scrappey_create_session This tool initiates an external browser session on the Scrappey platform, which is an active operation that allocates remote resources and triggers external infrastructure. Execute · High scrappey_request Sending arbitrary HTTP requests is an Execute-level action because the effects are entirely determined by the arguments.

4 of Scrappey MCP Server's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Scrappey MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Scrappey MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "scrappey_destroy_session": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Cap read operations

{
  "scrappey_list_sessions": {
    "limits": [
      {
        "counter": "scrappey_list_sessions_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Scrappey MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SCRAPPEY →

Instant setup, no code required.

FULL CATALOGUE

All 7 Scrappey MCP Server tools

DESTRUCTIVE 1 tools

Destructive scrappey_destroy_session Destroy an existing browser session in Scrappey to free resources

EXECUTE 3 tools

Execute scrappey_browser_action Execute browser automation actions in a session. Supports clicking, typing, scrolling, waiting, JavaScript exe Execute scrappey_create_session Create a new browser session in Scrappey. Sessions persist browser state (cookies, localStorage) across reques Execute scrappey_request Send an HTTP request through Scrappey

READ 3 tools

Read scrappey_list_sessions List all active sessions for the current user Read scrappey_screenshot Take a screenshot of a webpage. Optionally execute browser actions before capturing. Read scrappey_session_active Check if a specific session is currently active

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Scrappey MCP Server

Can an AI agent delete data through the Scrappey MCP Server MCP server? +

Yes. The Scrappey MCP Server server exposes 1 destructive tools including scrappey_destroy_session. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How many tools does the Scrappey MCP Server MCP server expose? +

7 tools across 4 categories: Destructive, Execute, Read, Write. 3 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Scrappey MCP Server? +

Register the Scrappey MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Scrappey MCP Server tool call.

Deterministic rules across all 7 Scrappey MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SCRAPPEY →

Instant setup, no code required.

7 Scrappey MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.