AI agents use create-user-data 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.
The tool creates new user data records, which is a reversible write operation (data can be modified or deleted). However, severity is elevated to 'high' because user data creation in a CMS can have security implications (account creation, privilege assignment, etc.) if misused by an agent. It does not meet the threshold for Execute (no code execution), Destructive (reversible), or Financial (no money movement).
From the tool's definition Tool name 'create-user-data' and description 'Creates a new user data record' indicate data creation/modification. In CMS context, creating user data is a write operation with potential security implications.
Attacks that exploit this kind of access
Creates a new user data record. 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 create-user-data: 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.
create-user-data 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 create-user-data 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 create-user-data. 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.
create-user-data 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 →