import_recipe_from_url
Fetch, validate, and import a recipe or recipe-bundle JSON from an HTTPS URL into a local recipes directory (host-allowlisted, size-capped).
This record as markdown: /tools/io-github-pantani-tdmcp/import-recipe-from-url.md
What import_recipe_from_url does on tdmcp — TouchDesigner MCP server
AI agents use import_recipe_from_url 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_from_url is rated Medium
The tool creates or adds recipe data to the filesystem (Write category). Severity is medium rather than high because: (1) imports are reversible (recipes can be deleted), (2) scope is limited to recipes directory with allowlisting and size caps, and (3) the data source is validated and from HTTPS URLs only.
From the tool's definition Tool description explicitly states it will 'import...into a local recipes directory', and the name contains 'import'. This modifies local state by adding data to the recipes directory.
Attacks that exploit this kind of access
The rule that runs import_recipe_from_url 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_from_url, this is the rule to start with:
import_recipe_from_url 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_from_url call is checked against it from then on.
Questions about import_recipe_from_url
Fetch, validate, and import a recipe or recipe-bundle JSON from an HTTPS URL into a local recipes directory (host-allowlisted, size-capped). 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_from_url: 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_from_url 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_from_url 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_from_url. 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_from_url 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