td_execute · Td MCP: Risk & Policy

WHAT IT DOES

What td_execute does on Td

AI agents invoke td_execute to trigger actions in Td. 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 td_execute needs a policy

This tool allows execution of Python code within TouchDesigner, which can trigger complex operations, manipulate the application state, access external resources, and cause side effects that depend on the code passed as arguments.

From the tool's definition Tool name is 'td_execute' and description states 'Execute Python code inside TouchDesigner.' This directly runs arbitrary code within TouchDesigner's runtime environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

td_execute Rate-limited

td_execute 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": {
    "td_execute": {
      "limits": [
        {
          "counter": "td_execute_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 Td, so you can run agents against it safely.

FAQ

Questions about td_execute

What does the td_execute tool do? +

Execute Python code inside TouchDesigner. It is categorised as a Execute tool in the Td MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on td_execute? +

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

What risk level is td_execute? +

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

Can I rate-limit td_execute? +

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

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

td_execute is provided by the Td MCP server (tai5863/td-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.