Delete a scan and all its data.
AI agents call delete_scan to permanently remove resources in SpiderFoot MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes scan records and associated data without reversibility. While the blast radius is bounded to scan artifacts rather than production systems, the irreversible nature of data deletion and potential loss of investigation records classifies this as Destructive rather than Write. The severity is high because misuse could result in loss of OSINT investigation work and audit trails.
From the tool's definition Tool name is 'delete_scan' with description 'Delete a scan and all its data.' The verb 'delete' combined with 'all its data' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a scan and all its data. It is categorised as a Destructive tool in the SpiderFoot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SpiderFoot MCP Server MCP server in PolicyLayer and add a rule for delete_scan: 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 SpiderFoot MCP Server. Nothing to install.
delete_scan 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_scan 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_scan. 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_scan is provided by the SpiderFoot MCP Server MCP server (marlinkcyber/spiderfoot-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 →