create_panic

Build a live-performance safety control — the

SERVERAos SOURCE@hybridlabor-api/aos

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/hybridlabor-api-aos/create-panic.md

WHAT IT DOES

What create_panic does on Aos

AI agents invoke create_panic to trigger actions in Aos. 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_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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_panic safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_panic, this is the rule to start with:

create_panic Rate-limited

create_panic 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_panic": {
      "limits": [
        {
          "counter": "create_panic_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 Aos, apply this rule, and every create_panic call is checked against it from then on.

FAQ

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 Aos 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 Aos 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 Aos. 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 Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos 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 →