Resume a stopped crawl job (API v2 POST /crawl/:id/resume).
AI agents invoke crawl_resume to trigger actions in Scrapegraph. 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.
This tool triggers an external operation (resuming a crawl job) via a POST request. It doesn't merely read data, nor does it create/modify data in a reversible write sense — it resumes an active process execution. The blast radius is medium since it restarts a potentially resource-consuming crawl operation.
From the tool's definition Resume a stopped crawl job (API v2 POST /crawl/:id/resume)
Documented attack patterns abuse exactly the kind of access crawl_resume gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Scrapegraph, and nothing reaches the server without passing your rules. This is the rule we recommend for crawl_resume:
{
"version": "1",
"default": "deny",
"tools": {
"crawl_resume": {
"limits": [
{
"counter": "crawl_resume_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}crawl_resume 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.
Free to start. No card required.
Resume a stopped crawl job (API v2 POST /crawl/:id/resume). It is categorised as a Execute tool in the Scrapegraph MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Scrapegraph MCP server in PolicyLayer and add a rule for crawl_resume: 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 Scrapegraph. Nothing to install.
crawl_resume is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the crawl_resume 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 crawl_resume. 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.
crawl_resume is provided by the Scrapegraph MCP server (ScrapeGraphAI/scrapegraph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Scrapegraph, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Scrapegraph tools catalogued and risk-classified — across an index of 43,000+ MCP servers.