Delete a blueprint
AI agents call delete_blueprint to permanently remove resources in Apstra MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a blueprint, which is a critical infrastructure artifact in Juniper Apstra. Deletion cannot be undone and would require manual recreation of potentially complex network configurations. The blast radius is significant in a datacenter environment where blueprints define production network topology, policies, and connectivity.
From the tool's definition Tool name is 'delete_blueprint' and description states 'Delete a blueprint'. Blueprints in datacenter network management are core configuration artifacts that represent entire network designs and deployments. Deletion is irreversible.
Attacks that exploit this kind of access
Delete a blueprint. It is categorised as a Destructive tool in the Apstra MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Apstra MCP Server MCP server in PolicyLayer and add a rule for delete_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 Apstra MCP Server. Nothing to install.
delete_blueprint is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_blueprint is provided by the Apstra MCP Server MCP server (vignitin/apstra-mcp-server). 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 →