scrapling_crawl_status
Check crawl progress and get collected items. Pass the session_id from scrapling_crawl. Returns status (running/completed/stopped), pages crawled, items with extracted data, and errors. Poll periodically until status is
This record as markdown: /tools/io-github-homenshum-nodebench/scrapling-crawl-status.md
What scrapling_crawl_status does on Nodebench
AI agents call scrapling_crawl_status to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why scrapling_crawl_status is rated Low
This tool retrieves status information and previously collected data from an ongoing or completed web crawl session. It performs polling queries without modifying, deleting, or executing anything. The primary action is to fetch and display status metrics and extracted results, making it a Read category tool with low severity since it has no side effects on target systems or data.
From the tool's definition Tool description states it "Check[s] crawl progress and get collected items" and "Returns status...pages crawled, items with extracted data, and errors." These are read/query operations with no mutation of data.
Attacks that exploit this kind of access
The rule that runs scrapling_crawl_status 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_status, this is the rule to start with:
scrapling_crawl_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every scrapling_crawl_status call is checked against it from then on.
Questions about scrapling_crawl_status
Check crawl progress and get collected items. Pass the session_id from scrapling_crawl. Returns status (running/completed/stopped), pages crawled, items with extracted data, and errors. Poll periodically until status is. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for scrapling_crawl_status: 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.
scrapling_crawl_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the scrapling_crawl_status 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.
Set action: deny in the PolicyLayer policy for scrapling_crawl_status. 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.
scrapling_crawl_status 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.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue