AI agents use export_fbx 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.
Export operations that generate new files or formats are classified as Write since they create new data artifacts. The severity is medium because exporting can consume disk space and create files that may overwrite existing exports with the same name in some contexts, but the operation is generally reversible (exported files can be deleted).
From the tool's definition The tool 'export_fbx' exports a node to FBX format, which creates a new file as output. The description indicates file creation/writing without deletion or irreversible destruction of existing data.
Documented attack patterns abuse exactly the kind of access export_fbx 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 export_fbx:
{
"version": "1",
"default": "deny",
"tools": {
"export_fbx": {
"limits": [
{
"counter": "export_fbx_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_fbx 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.
Export a node to FBX format. 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 export_fbx: 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.
export_fbx 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 export_fbx 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 export_fbx. 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.
export_fbx 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.