create_panic

Build a live-performance safety control — the

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-panic.md

What create_panic does on tdmcp — TouchDesigner MCP server

AI agents invoke create_panic 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.

Why create_panic is rated High

The tool name 'create_panic' and context of 'live-performance safety control' suggests it creates/triggers a panic/kill-switch mechanism in a live TouchDesigner performance environment. This likely executes an emergency control action (e.g., muting outputs, resetting nodes, triggering a blackout) with potentially broad effects on a live system. The description is truncated, lowering confidence.

From the tool's definition 'Build a live-performance safety control' — the description is truncated and uninformative beyond this phrase

Questions about create_panic

What does the create_panic tool do? +

Build a live-performance safety control — the. 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_panic? +

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

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

Can I rate-limit create_panic? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of tdmcp — TouchDesigner MCP server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.