Update a collaborative document with new content
AI agents use update-document to create or update resources in Tiptap Collaboration MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tiptap Collaboration MCP Server environment.
This tool creates or modifies data in a reversible manner. Updates can be undone through subsequent updates or version history features typical of collaborative document systems. It does not delete data (which would be Destructive) or execute arbitrary code (which would be Execute).
From the tool's definition Tool name 'update-document' and description 'Update a collaborative document with new content' explicitly indicate modification of existing data.
Documented attack patterns abuse exactly the kind of access update-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 update-document:
{
"version": "1",
"default": "deny",
"tools": {
"update-document": {
"limits": [
{
"counter": "update-document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-document stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update a collaborative document with new content. It is categorised as a Write tool in the Tiptap Collaboration MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tiptap Collaboration MCP Server MCP server in PolicyLayer and add a rule for update-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.
update-document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update-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 update-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.
update-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.