make_portable_tox
Save a COMP as a .tox package, write a tdmcp-component manifest beside it, and by default include a README.md documenting node inventory, custom parameters, inputs/outputs and external file references.
This record as markdown: /tools/io-github-pantani-tdmcp/make-portable-tox.md
What make_portable_tox does on tdmcp — TouchDesigner MCP server
AI agents use make_portable_tox to create or update resources in tdmcp — TouchDesigner MCP server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your tdmcp — TouchDesigner MCP server environment.
Why make_portable_tox is rated Medium
The tool creates and writes multiple files (a .tox package, manifest file, and documentation) to the filesystem. This is a Write operation because it creates new data artifacts reversibly — the written files can be modified or deleted. It does not execute arbitrary code, delete existing data irreversibly, or move financial resources.
From the tool's definition "Save a COMP as a .tox package, write a tdmcp-component manifest beside it, and by default include a README.md" — creates new files (.tox package, manifest, README.md) that are written to disk.
Attacks that exploit this kind of access
The rule that runs make_portable_tox safely
PolicyLayer is an MCP gateway: it sits between your AI agents and tdmcp — TouchDesigner MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For make_portable_tox, this is the rule to start with:
make_portable_tox 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.
The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every make_portable_tox call is checked against it from then on.
Questions about make_portable_tox
Save a COMP as a .tox package, write a tdmcp-component manifest beside it, and by default include a README.md documenting node inventory, custom parameters, inputs/outputs and external file references. It is categorised as a Write tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for make_portable_tox: 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 tdmcp — TouchDesigner MCP server. Nothing to install.
make_portable_tox 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 make_portable_tox 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 make_portable_tox. 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.
make_portable_tox is provided by the tdmcp — TouchDesigner MCP server MCP server (@dpantani/tdmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.
This server
Across the catalogue