Delete a reading journal entry by ID.
AI agents call delete_journal_entry 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 user data (journal entries) with no indicated undo or recovery mechanism. While the blast radius is limited to personal journal entries rather than system-wide data, deletion of user-generated content that cannot be reversed qualifies as Destructive.
From the tool's definition Tool name is 'delete_journal_entry' and description states 'Delete a reading journal entry by ID.' The verb 'delete' combined with irreversible removal of user-created journal content indicates destructive capability.
Attacks that exploit this kind of access
Delete a reading journal entry by ID. 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_journal_entry: 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_journal_entry 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_journal_entry 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_journal_entry. 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_journal_entry 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 →