pulse_parameter · Touchdesigner MCP: Risk & Policy

WHAT IT DOES

What pulse_parameter does on Touchdesigner

AI agents invoke pulse_parameter to trigger actions in Touchdesigner. 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 IT NEEDS A POLICY

Why pulse_parameter needs a policy

Pulsing a parameter triggers an external operation in TouchDesigner (like Reset or Trigger), which causes side effects that depend on the parameter being pulsed. This is an action that executes/triggers something rather than simply reading or writing data reversibly.

From the tool's definition Pulse a pulse-style parameter (e.g. a Reset or Trigger button)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pulse_parameter Rate-limited

pulse_parameter 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": {
    "pulse_parameter": {
      "limits": [
        {
          "counter": "pulse_parameter_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Touchdesigner, so you can run agents against it safely.

FAQ

Questions about pulse_parameter

What does the pulse_parameter tool do? +

Pulse a pulse-style parameter (e.g. a Reset or Trigger button). It is categorised as a Execute tool in the Touchdesigner MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pulse_parameter? +

Register the Touchdesigner MCP server in PolicyLayer and add a rule for pulse_parameter: 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 Touchdesigner. Nothing to install.

What risk level is pulse_parameter? +

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

Can I rate-limit pulse_parameter? +

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

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

pulse_parameter is provided by the Touchdesigner MCP server (mrinalghosh/touchdesigner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.