publish_recipe_bundle
Write a local, versioned recipe-bundle publish artifact for CI upload or handoff: <name>.recipes.json, tdmcp-recipe-publish.json, and tdmcp-checksums.json. Use recipe_ids for selected recipes or include_all=true for the whole library; overwrite=false protects existing artifacts. This is a filesys...
This record as markdown: /tools/io-github-pantani-tdmcp/publish-recipe-bundle.md
What publish_recipe_bundle does on tdmcp — TouchDesigner MCP server
AI agents use publish_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 publish_recipe_bundle is rated Medium
This tool creates or modifies files on the local filesystem in a reversible manner (can be deleted or overwritten). While it writes configuration/data files rather than destructive operations, the creation of versioned artifacts for CI/handoff represents a write operation with moderate blast radius if misused—an agent could publish incorrect recipe bundles, corrupt artifact chains, or disrupt CI pipelines.
From the tool's definition Tool description explicitly states 'Write a local, versioned recipe-bundle publish artifact' and mentions creating/writing three JSON files: '<name>.recipes.json', 'tdmcp-recipe-publish.json', and 'tdmcp-checksums.json'.
Attacks that exploit this kind of access
The rule that runs publish_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 publish_recipe_bundle, this is the rule to start with:
publish_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 publish_recipe_bundle call is checked against it from then on.
Questions about publish_recipe_bundle
Write a local, versioned recipe-bundle publish artifact for CI upload or handoff: <name>.recipes.json, tdmcp-recipe-publish.json, and tdmcp-checksums.json. Use recipe_ids for selected recipes or include_all=true for the whole library; overwrite=false protects existing artifacts. This is a filesystem write tool and returns artifact paths, checksum entries, included recipe count, and missing ids. 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 publish_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.
publish_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 publish_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 publish_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.
publish_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