AI agents use create_camera 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.
Creating a camera in a 3D modeling tool is a reversible Write operation—it adds a scene element that can be deleted or modified. It does not execute arbitrary code, delete data irreversibly, move money, or read existing data. The severity is medium because an AI could misuse this to create many cameras or misconfigure scene state, but the effects are contained to scene composition and easily undone.
From the tool's definition Tool name 'create_camera' indicates creation of a new scene element in Houdini. Sibling tools include 'create_geometry', 'create_light', 'create_node', and 'create_simulation', all of which are creation operations.
Documented attack patterns abuse exactly the kind of access create_camera 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 create_camera:
{
"version": "1",
"default": "deny",
"tools": {
"create_camera": {
"limits": [
{
"counter": "create_camera_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_camera 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.
create_camera. 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 create_camera: 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.
create_camera 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 create_camera 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 create_camera. 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.
create_camera 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.