Update a blueprint. Provide only the fields you want to change.
AI agents use update_blueprint to create or update resources in Morpheus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Morpheus MCP Server environment.
This tool modifies blueprint configurations in an HPE Morpheus cloud infrastructure system. Blueprints are templates used for provisioning resources, so updating them affects future deployments and resource allocation.
From the tool's definition Tool name 'update_blueprint' and description 'Update a blueprint' indicate modification of infrastructure configuration data. The phrase 'Provide only the fields you want to change' confirms reversible updates rather than deletion.
Attacks that exploit this kind of access
Update a blueprint. Provide only the fields you want to change. It is categorised as a Write tool in the Morpheus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for update_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 Morpheus MCP Server. Nothing to install.
update_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_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_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_blueprint is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). 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 →