import_recipe_bundle
Import recipes from a portable JSON bundle into a recipe directory. The inverse of export_recipe_bundle: each recipe is validated before it is written, so a malformed bundle fails loudly instead of corrupting the directory. Writes files (destructive).
This record as markdown: /tools/io-github-pantani-tdmcp/import-recipe-bundle.md
What import_recipe_bundle does on tdmcp — TouchDesigner MCP server
AI agents use import_recipe_bundle 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 import_recipe_bundle is rated Medium
This tool creates or modifies recipe files in a directory by importing from a JSON bundle. While files are written (and overwrites could occur), the operation is reversible—files can be re-imported or manually edited. The validation and fail-safe design further supports Write rather than Destructive. The action affects TouchDesigner project state but does not irreversibly destroy data or prevent undo.
From the tool's definition Tool description states 'Writes files' and performs import/write operations into a recipe directory. The note '(destructive)' in the description is a clarification about validation and failure modes, not an indication that the tool deletes data—it emphasizes…
Attacks that exploit this kind of access
The rule that runs import_recipe_bundle 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 import_recipe_bundle, this is the rule to start with:
import_recipe_bundle 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 import_recipe_bundle call is checked against it from then on.
Questions about import_recipe_bundle
Import recipes from a portable JSON bundle into a recipe directory. The inverse of export_recipe_bundle: each recipe is validated before it is written, so a malformed bundle fails loudly instead of corrupting the directory. Writes files (destructive). 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 import_recipe_bundle: 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.
import_recipe_bundle 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 import_recipe_bundle 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 import_recipe_bundle. 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.
import_recipe_bundle 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