AI agents use move-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.
Moving an element modifies the data structure and location metadata reversibly. This qualifies as Write rather than Destructive because the operation can be undone by moving the element back. It is more severe than Read due to its side effects on content organization, but less severe than Destructive or Execute operations.
From the tool's definition Tool name 'move-element' with description 'Move an element to a new location' indicates structural modification of content within Umbraco CMS.
Attacks that exploit this kind of access
Move an element to a new location. 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 move-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.
move-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 move-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 move-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.
move-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.
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 →