Delete a crawl from Screaming Frog's internal database to free disk space.
AI agents call delete_crawl to permanently remove resources in Screaming Frog — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes crawl data from the database without the ability to recover it. While the blast radius is limited to local Screaming Frog storage (not affecting external systems or financial operations), the destructive nature of irreversible data deletion classifies this as Destructive rather than Write.
From the tool's definition Tool name is 'delete_crawl' and description states 'Delete a crawl from Screaming Frog's internal database to free disk space.' The verb 'delete' combined with removal from a database indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a crawl from Screaming Frog's internal database to free disk space. It is categorised as a Destructive tool in the Screaming Frog MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Screaming Frog MCP server in PolicyLayer and add a rule for delete_crawl: 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 Screaming Frog. Nothing to install.
delete_crawl is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_crawl 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 delete_crawl. 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.
delete_crawl is provided by the Screaming Frog MCP server (marykovziridze/screaming-frog-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →