AI agents call delete_node to permanently remove resources in HoudiniMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a node from a Houdini scene is irreversible without manual undo/recovery. A misdirected agent call could remove critical scene geometry, simulations, or network structures that the user did not intend to delete. While not as severe as financial loss, the destructive nature and potential for significant scene corruption justify 'high' severity.
From the tool's definition Tool name is 'delete_node' and description states 'Delete a node from the Houdini network.' The verb 'delete' and irreversible removal of a node from a 3D scene graph are unambiguous destructive operations.
Documented attack patterns abuse exactly the kind of access delete_node gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HoudiniMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_node:
{
"version": "1",
"default": "deny",
"hide": [
"delete_node"
]
}delete_node disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a node from the Houdini network. It is categorised as a Destructive tool in the HoudiniMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Houdini MCP server in PolicyLayer and add a rule for delete_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 HoudiniMCP. Nothing to install.
delete_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_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_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_node is provided by the Houdini MCP server (katha-begin/houdini-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from HoudiniMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 HoudiniMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.