update-document-blueprint
Updates a document blueprint by Id
This record as markdown: /tools/mcp-dev/update-document-blueprint.md
What update-document-blueprint does on Mcp Dev
AI agents use update-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.
Why update-document-blueprint is rated Medium
This tool modifies existing data (document blueprints) reversibly. It does not delete, execute arbitrary code, or transfer funds, making it a Write operation. The severity is high because corrupting or maliciously modifying blueprints could affect all documents created from them, creating wide blast radius across content management operations.
From the tool's definition Tool updates a document blueprint by Id. The verb 'Updates' indicates modification of existing data. Document blueprints in CMS systems are templates used for creating documents, so modifications affect downstream content creation workflows.
Attacks that exploit this kind of access
The rule that runs update-document-blueprint 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-document-blueprint, this is the rule to start with:
update-document-blueprint 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-document-blueprint call is checked against it from then on.
Questions about update-document-blueprint
Updates a document blueprint by Id. 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-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.
update-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 update-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 update-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.
update-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.
More on Mcp Dev, and thousands of servers like it.
This server
Across the catalogue