delete_blueprint_node
Delete a node from a Blueprint graph by GUID.
This record as markdown: /tools/aadeshrao123-unreal-mcp/delete-blueprint-node.md
What delete_blueprint_node does on Unreal-MCP
AI agents call delete_blueprint_node to permanently remove resources in Unreal-MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_blueprint_node is rated Critical
This tool destroys data (a Blueprint node) irreversibly. Although Unreal Engine typically maintains undo history, the semantic purpose of this tool is deletion. Within the hierarchy of risk categories, Destructive is more severe than Write (which creates/modifies reversibly) and Write is the next-most-severe alternative.
From the tool's definition Tool name explicitly contains 'delete'; description states 'Delete a node from a Blueprint graph by GUID.' The action removes a node irreversibly from a Blueprint, which cannot be undone without manual restoration or undo history.
Attacks that exploit this kind of access
The rule that runs delete_blueprint_node safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_blueprint_node, this is the rule to start with:
delete_blueprint_node 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 Unreal-MCP, apply this rule, and every delete_blueprint_node call is checked against it from then on.
Questions about delete_blueprint_node
Delete a node from a Blueprint graph by GUID. It is categorised as a Destructive tool in the Unreal-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Unreal MCP server in PolicyLayer and add a rule for delete_blueprint_node: 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 Unreal-MCP. Nothing to install.
delete_blueprint_node 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_node 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_node. 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_node is provided by the Unreal MCP server (aadeshrao123/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unreal, and thousands of servers like it.
Across the catalogue