create_show_failover

SERVERtdmcp — TouchDesigner MCP server SOURCE@dpantani/tdmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pantani-tdmcp/create-show-failover.md

WHAT IT DOES

What create_show_failover does on tdmcp — TouchDesigner MCP server

AI agents invoke create_show_failover to trigger actions in tdmcp — TouchDesigner MCP server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why create_show_failover is rated High

This tool constructs and wires together a complex live system in TouchDesigner — including executable DAT scripts (CHOP-Execute DAT), CHOPs, TOPs, and automated watchdog logic. It triggers real-time execution of network nodes and scripts in a live show context. Misuse could disrupt a live visual production, causing incorrect failover behavior, signal loss, or show interruption.

From the tool's definition Build a live-show watchdog: a Switch TOP (blend=1 cross-dissolve) between a primary source TOP and an MP4 fallback, driven by an Info CHOP + watchdog CHOP-Execute DAT that trips on cook stall

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_show_failover 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 create_show_failover, this is the rule to start with:

create_show_failover Rate-limited

create_show_failover stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_show_failover": {
      "limits": [
        {
          "counter": "create_show_failover_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every create_show_failover call is checked against it from then on.

FAQ

Questions about create_show_failover

What does the create_show_failover tool do? +

Build a live-show watchdog: a Switch TOP (blend=1 cross-dissolve) between a primary source TOP (NDI/camera/Spout/Syphon path, or a synthetic noiseTOP when none is given) and an MP4 fallback (or a constantTOP when no file is given), driven by an Info CHOP + watchdog CHOP-Execute DAT that trips on cook stall (total_cooks delta stays flat for stall_ms) and, optionally, primary cook errors. A Filter CHOP smooths the integer Switch index into a fade_ms crossfade. Sticky-recover auto-returns to primary after recover_ms healthy; otherwise stays on fallback until Reset. Exposes Active / Stall_Ms / Fade_Ms / Sticky_Recover / Reset / Force_Fallback controls and a Null CHOP of status channels for bind_to_channel. Returns the container, output TOP, status CHOP, control names, and the operator paths. It is categorised as a Execute tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_show_failover? +

Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for create_show_failover: 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.

What risk level is create_show_failover? +

create_show_failover is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_show_failover? +

Yes. Add a rate_limit block to the create_show_failover 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.

How do I block create_show_failover completely? +

Set action: deny in the PolicyLayer policy for create_show_failover. 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.

What MCP server provides create_show_failover? +

create_show_failover 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.

KEEP EXPLORING

More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.

This server

All 334 tdmcp — TouchDesigner MCP server tools → High-risk tools on this server →

Across the catalogue

diagram_create on Templonix Lite MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →