update-element
Updates an element by Id. USE AS LAST RESORT ONLY. IMPORTANT: Prefer update-element-properties for changing individual property values — it is simpler and safer because it preserves everything else. Only use this tool when you must replace the element
This record as markdown: /tools/mcp-dev/update-element.md
What update-element does on Mcp Dev
AI agents use update-element 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-element is rated Medium
This tool modifies data in an Umbraco CMS by updating/replacing elements. It is reversible (data can be updated again), so it falls under Write rather than Destructive. The 'replace the element' language and warnings about being a last resort suggest broad impact on element data.
From the tool's definition Tool name is 'update-element' and description states 'Updates an element by Id' and 'when you must replace the element'.
Attacks that exploit this kind of access
The rule that runs update-element 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-element, this is the rule to start with:
update-element 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-element call is checked against it from then on.
Questions about update-element
Updates an element by Id. USE AS LAST RESORT ONLY. IMPORTANT: Prefer update-element-properties for changing individual property values — it is simpler and safer because it preserves everything else. Only use this tool when you must replace the element. 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-element: 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-element 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-element 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-element. 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-element 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