This record as markdown: /tools/io-github-pantani-tdmcp/run-macro-script.md
What run_macro_script does on tdmcp — TouchDesigner MCP server
AI agents invoke run_macro_script 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 run_macro_script is rated High
This tool runs/executes macro scripts rather than simply reading or writing data. Script execution falls under the Execute category because it triggers code that can have unpredictable side effects depending on the script contents. The incomplete description limits confidence slightly, but the 'run_macro_script' name is sufficiently explicit about executing code.
From the tool's definition Tool name 'run_macro_script' and description 'Replay a' indicate execution of macro scripts in TouchDesigner. Macro scripts in TouchDesigner are code-execution mechanisms that can trigger arbitrary operations within the visual system.
Attacks that exploit this kind of access
The rule that runs run_macro_script 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 run_macro_script, this is the rule to start with:
run_macro_script 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 run_macro_script call is checked against it from then on.
Questions about run_macro_script
Replay a. 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 run_macro_script: 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.
run_macro_script 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 run_macro_script 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 run_macro_script. 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.
run_macro_script 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