AI agents use connect_nodes to create or update resources in HoudiniMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HoudiniMCP environment.
In Houdini, connecting nodes creates relationships between nodes in the node graph (e.g., wiring outputs to inputs). This is a reversible modification to the scene graph — a Write operation. The empty description lowers confidence, but the name strongly implies creating connections rather than deleting or executing code. Severity is medium as misuse could corrupt scene graph wiring but is generally reversible.
From the tool's definition Tool name 'connect_nodes' and server context of Houdini 3D scene manipulation; description is empty.
Documented attack patterns abuse exactly the kind of access connect_nodes 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 connect_nodes:
{
"version": "1",
"default": "deny",
"tools": {
"connect_nodes": {
"limits": [
{
"counter": "connect_nodes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}connect_nodes stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
connect_nodes. It is categorised as a Write tool in the HoudiniMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Houdini MCP server in PolicyLayer and add a rule for connect_nodes: 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.
connect_nodes 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 connect_nodes 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 connect_nodes. 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.
connect_nodes 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.