scrapling_crawl_stop

Stop a running crawl session. Pass the session_id from scrapling_crawl. Items collected so far are preserved. Use when you have enough data or need to abort. Requires Scrapling bridge server.

SERVERNodebench SOURCEnodebench-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/scrapling-crawl-stop.md

WHAT IT DOES

What scrapling_crawl_stop does on Nodebench

AI agents invoke scrapling_crawl_stop to trigger actions in Nodebench. 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.

RISK

Why scrapling_crawl_stop is rated High

This tool executes a command to stop an external web scraping service. While the operation is reversible (a new crawl can be started), it actively triggers an external system state change via the Scrapling bridge server, making it Execute rather than Read or Write.

From the tool's definition Tool description states 'Stop a running crawl session' and 'abort' - it triggers an external operation (stopping a web scraping session) whose effects depend on the session_id argument.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs scrapling_crawl_stop safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scrapling_crawl_stop, this is the rule to start with:

scrapling_crawl_stop Rate-limited

scrapling_crawl_stop 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": {
    "scrapling_crawl_stop": {
      "limits": [
        {
          "counter": "scrapling_crawl_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every scrapling_crawl_stop call is checked against it from then on.

FAQ

Questions about scrapling_crawl_stop

What does the scrapling_crawl_stop tool do? +

Stop a running crawl session. Pass the session_id from scrapling_crawl. Items collected so far are preserved. Use when you have enough data or need to abort. Requires Scrapling bridge server. It is categorised as a Execute tool in the Nodebench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scrapling_crawl_stop? +

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

What risk level is scrapling_crawl_stop? +

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

Can I rate-limit scrapling_crawl_stop? +

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

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

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

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →