AI agents use set_parameter 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.
The name 'set_parameter' implies writing/modifying data (setting a value), which is a reversible modification. Given the context of a Houdini MCP server focused on 3D scene control, this likely sets a parameter on a Houdini node. The description is empty, which lowers confidence. Severity is medium as misconfigured parameters could corrupt scene elements but are generally recoverable.
From the tool's definition Tool name 'set_parameter' suggests modifying a parameter value on a node or object within Houdini.
Documented attack patterns abuse exactly the kind of access set_parameter 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 set_parameter:
{
"version": "1",
"default": "deny",
"tools": {
"set_parameter": {
"limits": [
{
"counter": "set_parameter_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_parameter 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.
set_parameter. 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 set_parameter: 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.
set_parameter 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 set_parameter 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 set_parameter. 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.
set_parameter 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.