export_network_to_vault
READ an existing TD network
This record as markdown: /tools/io-github-pantani-tdmcp/export-network-to-vault.md
What export_network_to_vault does on tdmcp — TouchDesigner MCP server
AI agents call export_network_to_vault to retrieve information from tdmcp — TouchDesigner MCP server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why export_network_to_vault is rated Low
The description explicitly says this is a read operation on an existing TouchDesigner network. However, the tool name 'export_network_to_vault' suggests it may also write/store data to a vault location, which could involve a Write action. The description takes precedence for classification but lowers confidence slightly. If it truly only reads, severity is low.
From the tool's definition Tool description states 'READ an existing TD network'
Attacks that exploit this kind of access
The rule that runs export_network_to_vault 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_network_to_vault, this is the rule to start with:
export_network_to_vault is read-only, so it stays allowed. 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_network_to_vault call is checked against it from then on.
Questions about export_network_to_vault
READ an existing TD network. It is categorised as a Read tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it retrieves data without modifying state.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for export_network_to_vault: 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_network_to_vault is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the export_network_to_vault 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_network_to_vault. 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_network_to_vault 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