update-document
Updates a document by Id. USE AS LAST RESORT ONLY. IMPORTANT: Prefer these specialized tools instead: - update-document-name: For renaming a document (or a specific culture variant) - the safe way to change the name - update-document-properties: For updating individual property values (simpler, s...
This record as markdown: /tools/mcp-dev/update-document.md
What update-document does on Mcp Dev
AI agents use update-document to create or update resources in Mcp Dev, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Dev environment.
Why update-document is rated Medium
This tool modifies data in an Umbraco CMS by updating documents. While it creates or alters data reversibly (rather than deleting it irreversibly), the broad scope of changes it can make—including document-level metadata, templates, and variants—and the explicit warning to use it only as a last resort places it in the Write category with high severity.
From the tool's definition Tool name is 'update-document' and description states it 'Updates a document by Id.' The description explicitly warns 'USE AS LAST RESORT ONLY' and advises preferring specialized tools for safer updates, indicating this tool performs broad document…
Attacks that exploit this kind of access
The rule that runs update-document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update-document, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every update-document call is checked against it from then on.
Questions about update-document
Updates a document by Id. USE AS LAST RESORT ONLY. IMPORTANT: Prefer these specialized tools instead: - update-document-name: For renaming a document (or a specific culture variant) - the safe way to change the name - update-document-properties: For updating individual property values (simpler, safer) - update-block-property: For updating properties within BlockList/BlockGrid/RichText blocks Only use this tool when you need to update document-level metadata (template, variants) or when the specialized tools cannot handle your specific use case. If you must use this tool: - Always read the current document value first - Only update the required values - Don. It is categorised as a Write tool in the Mcp Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Dev 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 Mcp Dev. 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 Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Dev, and thousands of servers like it.
This server
Across the catalogue