Remove a tag from a Readwise highlight or book.
AI agents call delete_readwise_tag to permanently remove resources in Kiseki-Labs-Readwise-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes tag associations from Readwise documents. While not as severe as deleting entire documents or highlights, tag deletion is irreversible and removes user-applied metadata. The action cannot be undone programmatically and represents data loss.
From the tool's definition Tool name is 'delete_readwise_tag' and description states 'Remove a tag from a Readwise highlight or book.' The verb 'delete' and 'remove' indicate irreversible deletion of tag metadata.
Documented attack patterns abuse exactly the kind of access delete_readwise_tag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kiseki-Labs-Readwise-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_readwise_tag:
{
"version": "1",
"default": "deny",
"hide": [
"delete_readwise_tag"
]
} delete_readwise_tag 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.
Remove a tag from a Readwise highlight or book. It is categorised as a Destructive tool in the Kiseki-Labs-Readwise-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kiseki-Labs-Readwise- MCP server in PolicyLayer and add a rule for delete_readwise_tag: 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 Kiseki-Labs-Readwise-MCP. Nothing to install.
delete_readwise_tag 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_readwise_tag 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_readwise_tag. 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_readwise_tag is provided by the Kiseki-Labs-Readwise- MCP server (kiseki-technologies/kiseki-labs-readwise-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kiseki-Labs-Readwise-MCP, 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.
8 Kiseki-Labs-Readwise-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.