export_setlist_to_vault
Serialize the current cues stored on a COMP (manage_cue snapshots, keyed
This record as markdown: /tools/io-github-pantani-tdmcp/export-setlist-to-vault.md
What export_setlist_to_vault does on tdmcp — TouchDesigner MCP server
AI agents use export_setlist_to_vault 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_setlist_to_vault is rated Medium
This tool writes/exports data (cues and snapshots) to persistent storage (a vault). While it modifies state by storing configuration data, it is reversible (exported data can be re-imported or overwritten), making it Write rather than Destructive.
From the tool's definition Tool name 'export_setlist_to_vault' indicates serialization and storage of cues/snapshots to a vault, which creates or persists data. Description mentions 'Serialize the current cues stored on a COMP' and references to snapshots and keyed data structures.
Attacks that exploit this kind of access
The rule that runs export_setlist_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_setlist_to_vault, this is the rule to start with:
export_setlist_to_vault 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_setlist_to_vault call is checked against it from then on.
Questions about export_setlist_to_vault
Serialize the current cues stored on a COMP (manage_cue snapshots, keyed. 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_setlist_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_setlist_to_vault 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_setlist_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_setlist_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_setlist_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