AI agents use create-document-blueprint 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 data structures (document blueprints) within Umbraco CMS, which is a Write operation. Creation is reversible through deletion. Severity is medium because unauthorized blueprint creation could pollute the content structure and require administrative cleanup, but lacks the irreversibility of Destructive operations or the financial impact of Financial operations.
From the tool's definition Tool name 'create-document-blueprint' and description 'Creates a new document blueprint' indicate data creation in Umbraco CMS. Document blueprints are templated content structures, so this creates new reversible content objects.
Attacks that exploit this kind of access
Creates a new document blueprint. 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-document-blueprint: 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-document-blueprint 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-document-blueprint 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-document-blueprint. 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-document-blueprint 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 →