Delete a tiddler. Shows current content and requests approval before deleting.
AI agents call delete_tiddler to permanently remove resources in TiddlyWiki MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on wiki content. Although the description mentions requesting approval before deleting (a safety measure), the core action is destructive—once a tiddler is deleted, it cannot be recovered through normal means. This falls under the Destructive category rather than Write, as deletion is not reversible.
From the tool's definition Tool name is 'delete_tiddler' and description states it will 'Delete a tiddler'. This irreversibly removes data from the TiddlyWiki.
Attacks that exploit this kind of access
Delete a tiddler. Shows current content and requests approval before deleting. It is categorised as a Destructive tool in the TiddlyWiki MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TiddlyWiki MCP Server MCP server in PolicyLayer and add a rule for delete_tiddler: 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 TiddlyWiki MCP Server. Nothing to install.
delete_tiddler 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_tiddler 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_tiddler. 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_tiddler is provided by the TiddlyWiki MCP Server MCP server (ppetru/tiddlywiki-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 →