AI agents use move-document-type 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 a document type to a new location is a write operation as it modifies the organizational structure of existing content management data. While reversible, it could have cascading effects on dependent content and workflows if misused by an agent. Severity is medium because the impact is scoped to organizational metadata rather than content itself, and the action can be undone by moving it back.
From the tool's definition Tool name 'move-document-type' and description 'Move a document type to a new location' indicate modification of existing data structure organization.
Attacks that exploit this kind of access
Move a document type 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-document-type: 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-document-type 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-document-type 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-document-type. 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-document-type 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 →