export_externalized_tree
Save a COMP as a git-diffable externalized .tox tree using TouchDesigner
This record as markdown: /tools/io-github-pantani-tdmcp/export-externalized-tree.md
What export_externalized_tree does on tdmcp — TouchDesigner MCP server
AI agents use export_externalized_tree 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 export_externalized_tree is rated Medium
The tool creates/modifies externalized TouchDesigner component files (.tox format). This is a Write operation because it creates or modifies data reversibly — the exported files can be re-imported, edited, or reverted via version control (git-diffable format supports this). It does not delete data (so not Destructive), does not execute arbitrary code (Execute), and has no financial impact.
From the tool's definition Tool description states 'Save a COMP as a git-diffable externalized .tox tree' — 'save' indicates creating or modifying files in a persistent format (.tox files are TouchDesigner component files).
Attacks that exploit this kind of access
The rule that runs export_externalized_tree 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 export_externalized_tree, this is the rule to start with:
export_externalized_tree 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 export_externalized_tree call is checked against it from then on.
Questions about export_externalized_tree
Save a COMP as a git-diffable externalized .tox tree using TouchDesigner. 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 export_externalized_tree: 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.
export_externalized_tree 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_externalized_tree 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_externalized_tree. 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_externalized_tree 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