connect_isadora_patch
Create an Isadora OSC actor, watcher, and scene exchange scaffold with stable namespace mapping.
This record as markdown: /tools/io-github-pantani-tdmcp/connect-isadora-patch.md
What connect_isadora_patch does on tdmcp — TouchDesigner MCP server
AI agents use connect_isadora_patch 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 connect_isadora_patch is rated Medium
This tool creates or generates new objects (OSC actor, watcher, scene exchange scaffold) rather than reading existing data. It modifies the project state by introducing new components with configured namespace mappings. This is a Write operation—reversible object creation—rather than Execute (which would run arbitrary code based on parameters) or Destructive (which would delete).
From the tool's definition Tool creates OSC actor, watcher, and scene exchange scaffold—new components with persistent configuration (stable namespace mapping). The description indicates creation of artifacts in the TouchDesigner/Isadora environment.
Attacks that exploit this kind of access
The rule that runs connect_isadora_patch 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 connect_isadora_patch, this is the rule to start with:
connect_isadora_patch 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 connect_isadora_patch call is checked against it from then on.
Questions about connect_isadora_patch
Create an Isadora OSC actor, watcher, and scene exchange scaffold with stable namespace mapping. 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 connect_isadora_patch: 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.
connect_isadora_patch 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 connect_isadora_patch 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 connect_isadora_patch. 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.
connect_isadora_patch 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