create_engine_comp

Drop a TouchDesigner Engine COMP that loads an external .tox in a separate TD subprocess —

High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pantani-tdmcp/create-engine-comp.md

What create_engine_comp does on tdmcp — TouchDesigner MCP server

AI agents invoke create_engine_comp 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 create_engine_comp is rated High

The tool executes an external file (.tox) inside a separate TouchDesigner subprocess. This is an Execute-category action because it triggers an external process whose effects depend on the content of the loaded file. The blast radius is high because arbitrary .tox files could contain any logic, network calls, or system interactions when executed as a subprocess.

From the tool's definition 'loads an external .tox in a separate TD subprocess' — this spawns a subprocess and executes an external TouchDesigner component file (.tox)

Questions about create_engine_comp

What does the create_engine_comp tool do? +

Drop a TouchDesigner Engine COMP that loads an external .tox in a separate TD subprocess —. 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.

How do I enforce a policy on create_engine_comp? +

Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for create_engine_comp: 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.

What risk level is create_engine_comp? +

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

Can I rate-limit create_engine_comp? +

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

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

create_engine_comp 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of tdmcp — TouchDesigner MCP server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.