scrappey_request · Scrappey MCP Server MCP: Risk & Policy

WHAT IT DOES

What scrappey_request does on Scrappey MCP Server

AI agents invoke scrappey_request 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_request needs a policy

Sending arbitrary HTTP requests is an Execute-level action because the effects are entirely determined by the arguments. It could read data, write data, or trigger destructive operations on external services. The most severe common case is Execute, and it could reach Destructive or Financial depending on the target endpoint, but without more specifics Execute is the correct base classification.

From the tool's definition Send an HTTP request through Scrappey — triggers external HTTP operations whose effects depend on the method and URL arguments (could be GET, POST, DELETE, etc.)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scrappey_request Rate-limited

scrappey_request 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_request": {
      "limits": [
        {
          "counter": "scrappey_request_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_request

What does the scrappey_request tool do? +

Send an HTTP request through Scrappey. 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_request? +

Register the Scrappey MCP Server MCP server in PolicyLayer and add a rule for scrappey_request: 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_request? +

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

Can I rate-limit scrappey_request? +

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

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

scrappey_request 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.