pulse_td_parameter
Validate that an existing operator parameter is Pulse style, invoke its structured .pulse() operation, and confirm the result. Missing operators, missing parameters and non-Pulse styles return typed bridge errors. Does not use raw Python fallback.
This record as markdown: /tools/io-github-pantani-tdmcp/pulse-td-parameter.md
What pulse_td_parameter does on tdmcp — TouchDesigner MCP server
AI agents invoke pulse_td_parameter 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 pulse_td_parameter is rated High
This tool executes a specific operation (.pulse()) on TouchDesigner parameters, which can trigger visual effects, animations, or state changes in the real-time graphics system. The effects are parameter-dependent and not reversible through this tool alone, but the operation itself is not destructive (doesn't delete data).
From the tool's definition The tool invokes a structured .pulse() operation on a TouchDesigner operator parameter. Pulse operations trigger actions or state changes in TouchDesigner's visual system whose effects depend on the parameter being targeted.
Attacks that exploit this kind of access
The rule that runs pulse_td_parameter 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 pulse_td_parameter, this is the rule to start with:
pulse_td_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.
The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every pulse_td_parameter call is checked against it from then on.
Questions about pulse_td_parameter
Validate that an existing operator parameter is Pulse style, invoke its structured .pulse() operation, and confirm the result. Missing operators, missing parameters and non-Pulse styles return typed bridge errors. Does not use raw Python fallback. 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.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for pulse_td_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 tdmcp — TouchDesigner MCP server. Nothing to install.
pulse_td_parameter is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pulse_td_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.
Set action: deny in the PolicyLayer policy for pulse_td_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.
pulse_td_parameter 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.
Across the catalogue