delete_blueprint
Delete an installed blueprint by its relative path (e.g. 'author/blueprint_name.yaml').
This record as markdown: /tools/fistacho-ha-nexus-agent/delete-blueprint.md
What delete_blueprint does on Ha Nexus Agent
AI agents call delete_blueprint to permanently remove resources in Ha Nexus Agent, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_blueprint is rated Critical
This tool permanently removes a blueprint from Home Assistant, which is a data deletion operation that cannot be undone. Blueprints are configured automation/script templates that users rely on; deleting one would irreversibly destroy that configuration unless a backup exists.
From the tool's definition Tool description: 'Delete an installed blueprint by its relative path' — the verb 'Delete' explicitly indicates irreversible removal of data (a blueprint file).
Attacks that exploit this kind of access
The rule that runs delete_blueprint safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ha Nexus Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_blueprint, this is the rule to start with:
delete_blueprint is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every delete_blueprint call is checked against it from then on.
Questions about delete_blueprint
Delete an installed blueprint by its relative path (e.g. 'author/blueprint_name.yaml'). It is categorised as a Destructive tool in the Ha Nexus Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ha Nexus Agent 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 Ha Nexus Agent. 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 Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ha Nexus Agent, and thousands of servers like it.
Across the catalogue