Delete a collaborative document
AI agents call delete-document to permanently remove resources in Tiptap Collaboration MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible operation that cannot be undone—deleting a collaborative document removes it permanently from the system. This is the defining characteristic of the Destructive category. While the blast radius is high (loss of collaborative work), it is not Financial or critical system-level compromise, justifying 'high' severity rather than 'critical'.
From the tool's definition Tool name 'delete-document' with description 'Delete a collaborative document' explicitly indicates irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access delete-document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tiptap Collaboration MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-document:
{
"version": "1",
"default": "deny",
"hide": [
"delete-document"
]
} 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 a collaborative document. It is categorised as a Destructive tool in the Tiptap Collaboration MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tiptap Collaboration MCP Server MCP server in PolicyLayer and add a rule for 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 Tiptap Collaboration MCP Server. Nothing to install.
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 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 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.
delete-document is provided by the Tiptap Collaboration MCP Server MCP server (trainual/tiptap-collaboration-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tiptap Collaboration 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.
11 Tiptap Collaboration MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.