save_recipe_to_vault
Capture an existing COMP
This record as markdown: /tools/io-github-pantani-tdmcp/save-recipe-to-vault.md
What save_recipe_to_vault does on tdmcp — TouchDesigner MCP server
AI agents use save_recipe_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 save_recipe_to_vault is rated Medium
This tool creates or stores a new recipe configuration in a vault, which is a reversible write operation. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), involves no financial transaction (not Financial), and does not merely query data (not Read).
From the tool's definition Tool name 'save_recipe_to_vault' and description 'Capture an existing COMP' indicate persisting/storing data (a recipe) to a vault system. The 'save' and 'to_vault' language denotes creation or storage of a new artifact.
Attacks that exploit this kind of access
The rule that runs save_recipe_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 save_recipe_to_vault, this is the rule to start with:
save_recipe_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 save_recipe_to_vault call is checked against it from then on.
Questions about save_recipe_to_vault
Capture an existing COMP. 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 save_recipe_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.
save_recipe_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 save_recipe_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 save_recipe_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.
save_recipe_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