librecrawl_audit_cancel
Terminal stop. Upstream crawl is stopped; partial artifacts are kept where written.
This record as markdown: /tools/adityaarsharma-librecrawl-technical-seo-audit-mcp/librecrawl-audit-cancel.md
What librecrawl_audit_cancel does on Librecrawl Technical Seo Audit
AI agents call librecrawl_audit_cancel to permanently remove resources in Librecrawl Technical Seo Audit, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why librecrawl_audit_cancel is rated Critical
This tool irreversibly terminates an in-progress crawl operation. Once cancelled, the crawl cannot be resumed — it is a terminal stop. While partial artifacts are preserved, the crawl state itself is permanently destroyed and cannot be undone, placing it in the Destructive category. Severity is medium because it affects only an ongoing audit job rather than persistent business-critical data.
From the tool's definition Terminal stop. Upstream crawl is stopped; partial artifacts are kept where written.
Attacks that exploit this kind of access
The rule that runs librecrawl_audit_cancel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Librecrawl Technical Seo Audit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For librecrawl_audit_cancel, this is the rule to start with:
librecrawl_audit_cancel is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Librecrawl Technical Seo Audit, apply this rule, and every librecrawl_audit_cancel call is checked against it from then on.
Questions about librecrawl_audit_cancel
Terminal stop. Upstream crawl is stopped; partial artifacts are kept where written. It is categorised as a Destructive tool in the Librecrawl Technical Seo Audit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Librecrawl Technical Seo Audit MCP server in PolicyLayer and add a rule for librecrawl_audit_cancel: 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 Librecrawl Technical Seo Audit. Nothing to install.
librecrawl_audit_cancel 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 librecrawl_audit_cancel 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 librecrawl_audit_cancel. 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.
librecrawl_audit_cancel is provided by the Librecrawl Technical Seo Audit MCP server (adityaarsharma/librecrawl-technical-seo-audit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Librecrawl Technical Seo Audit, and thousands of servers like it.
Across the catalogue