create_safety_blackout_chain

SERVERtdmcp — TouchDesigner MCP server SOURCE@dpantani/tdmcp

Medium RISK CLASS

Category Write

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-safety-blackout-chain.md

WHAT IT DOES

What create_safety_blackout_chain does on tdmcp — TouchDesigner MCP server

AI agents use create_safety_blackout_chain 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.

RISK

Why create_safety_blackout_chain is rated Medium

This tool creates a new node chain (container, composite, output nodes, etc.) in the TouchDesigner project. It is a Write operation — it builds and configures network nodes reversibly. While it involves 'emergency' and 'blackout' language, these are UI/visual safety controls, not destructive data deletion. No code execution at cook time is explicitly noted ('no Python runs at cook time').

From the tool's definition 'Build a live-show safety primitive', 'Returns the container, source, dim, emergency-gate, composite, and output node' — creates and wires nodes in the TouchDesigner network

Attacks that exploit this kind of access

RECOMMENDED RULE

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

create_safety_blackout_chain Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_safety_blackout_chain": {
      "limits": [
        {
          "counter": "create_safety_blackout_chain_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_safety_blackout_chain call is checked against it from then on.

FAQ

Questions about create_safety_blackout_chain

What does the create_safety_blackout_chain tool do? +

Build a live-show safety primitive at the very end of the master output chain: deterministic fade-to-black over a configurable time, optional emergency single-frame hard-cut, optional hotkey + external watchdog trigger, and symmetric fade-in recovery. All reactivity is parameter-driven (Speed + Lookup CHOP + Math/Logic CHOPs) — no Python runs at cook time, so the chain is ALLOW_EXEC=0-safe. Complements create_panic (per-source kill+freeze) by being the master-output dimmer with grace, recovery, and a watchdog hook. Returns the container, source, dim, emergency-gate, composite, and output node paths plus the trigger merge/target/speed/lookup nodes. 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.

How do I enforce a policy on create_safety_blackout_chain? +

Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for create_safety_blackout_chain: 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_safety_blackout_chain? +

create_safety_blackout_chain is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_safety_blackout_chain? +

Yes. Add a rate_limit block to the create_safety_blackout_chain 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_safety_blackout_chain completely? +

Set action: deny in the PolicyLayer policy for create_safety_blackout_chain. 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_safety_blackout_chain? +

create_safety_blackout_chain 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 →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →