author_script_operator
Scaffold a Script CHOP/DAT/SOP/TOP with a ready-to-edit onCook(scriptOp) stub and optional custom parameters. Creates the Script op plus its companion callbacks DAT, writes a per-family stub (chan/row/point/numpy) — or your
This record as markdown: /tools/io-github-pantani-tdmcp/author-script-operator.md
What author_script_operator does on tdmcp — TouchDesigner MCP server
AI agents use author_script_operator to create or update resources in tdmcp — TouchDesigner MCP server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your tdmcp — TouchDesigner MCP server environment.
Why author_script_operator is rated Medium
This tool creates and modifies TouchDesigner script operators by writing code scaffolds and callbacks. While it does create executable scripts (which might suggest Execute), the primary action is authoring and writing the script structure itself, which is reversible — scripts can be deleted or modified. The tool does not execute the scripts it creates, only scaffolds them for user editing.
From the tool's definition Tool description states it 'Creates the Script op plus its companion callbacks DAT, writes a per-family stub' — explicitly creating new operators and writing code scaffolds. The action is 'author_script_operator' which creates/generates new executable scripts.
Attacks that exploit this kind of access
The rule that runs author_script_operator 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 author_script_operator, this is the rule to start with:
author_script_operator stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 author_script_operator call is checked against it from then on.
Questions about author_script_operator
Scaffold a Script CHOP/DAT/SOP/TOP with a ready-to-edit onCook(scriptOp) stub and optional custom parameters. Creates the Script op plus its companion callbacks DAT, writes a per-family stub (chan/row/point/numpy) — or your. It is categorised as a Write tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for author_script_operator: 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.
author_script_operator is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the author_script_operator 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 author_script_operator. 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.
author_script_operator 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.
This server
Across the catalogue