Delete one or more documents from your Readwise Reader library.
AI agents call reader_delete_document to permanently remove resources in Reader MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of documents is irreversible and cannot be undone. This is a destructive operation that permanently removes user data from their personal knowledge repository. While the blast radius is limited to the user's own Readwise library (not system-wide), the permanent loss of potentially important documents justifies 'high' severity and the Destructive category, which takes precedence over Write operations.
From the tool's definition Tool description states 'Delete one or more documents from your Readwise Reader library.' The verb 'delete' combined with 'one or more documents' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access reader_delete_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reader MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for reader_delete_document:
{
"version": "1",
"default": "deny",
"hide": [
"reader_delete_document"
]
}reader_delete_document disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete one or more documents from your Readwise Reader library. It is categorised as a Destructive tool in the Reader MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Reader MCP Server MCP server in PolicyLayer and add a rule for reader_delete_document: 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 Reader MCP Server. Nothing to install.
reader_delete_document 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 reader_delete_document 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 reader_delete_document. 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.
reader_delete_document is provided by the Reader MCP Server MCP server (xinthink/reader-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reader MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Reader MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.