Evaluate a single Python expression in TD and return its value.
AI agents invoke eval_python 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.
Executing arbitrary Python expressions is an Execute-category action. Despite being framed as 'eval' (read-like), Python expressions can have side effects, access the filesystem, network, or system resources. The blast radius is high because a malicious or mistaken expression could manipulate the TouchDesigner environment, exfiltrate data, or cause unintended system interactions.
From the tool's definition "Evaluate a single Python expression in TD and return its value" — runs arbitrary Python code inside TouchDesigner
Attacks that exploit this kind of access
Evaluate a single Python expression in TD and return its value. 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.
Register the Touchdesigner MCP server in PolicyLayer and add a rule for eval_python: 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.
eval_python 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 eval_python 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 eval_python. 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.
eval_python 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →