Delete a Hardcover list by ID. This cannot be undone.
AI agents call delete_list to permanently remove resources in Hardcover — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a user's list from the Hardcover library with no recovery option. While the blast radius is limited to a single list (not financial impact or system-wide effects), the irreversible deletion of user data warrants 'high' severity. The confidence is high because the description is explicit and unambiguous about the destructive and irreversible nature of the action.
From the tool's definition The tool description explicitly states 'Delete a Hardcover list by ID. This cannot be undone.' The irreversible nature ('cannot be undone') and deletion operation ('Delete') are the defining characteristics of the Destructive category.
Attacks that exploit this kind of access
Delete a Hardcover list by ID. This cannot be undone. It is categorised as a Destructive tool in the Hardcover MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hardcover MCP server in PolicyLayer and add a rule for delete_list: 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 Hardcover. Nothing to install.
delete_list 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_list 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_list. 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_list is provided by the Hardcover MCP server (kristianedlund/hardcover-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 →