create_3d_audio_reactive
Build a 3D scene that reacts to sound — the 3D counterpart of create_audio_reactive (use that for a 2D spectrum visual instead). Creates a new baseCOMP under
This record as markdown: /tools/io-github-pantani-tdmcp/create-3d-audio-reactive.md
What create_3d_audio_reactive does on tdmcp — TouchDesigner MCP server
AI agents use create_3d_audio_reactive 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 create_3d_audio_reactive is rated Medium
This tool creates or adds new components to a TouchDesigner scene, which is a reversible operation (components can be deleted or modified). It does not execute arbitrary code, destroy data, or move money. The severity is medium because while the modifications are recoverable, they affect the visual system design and could be misused to create unwanted scene complexity or resource consumption in the project.
From the tool's definition Tool creates a new baseCOMP (component) under a project, which is a reversible modification that adds new visual/audio elements to a TouchDesigner project. The description states 'Creates a new baseCOMP' indicating content creation.
Attacks that exploit this kind of access
The rule that runs create_3d_audio_reactive 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 create_3d_audio_reactive, this is the rule to start with:
create_3d_audio_reactive 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 create_3d_audio_reactive call is checked against it from then on.
Questions about create_3d_audio_reactive
Build a 3D scene that reacts to sound — the 3D counterpart of create_audio_reactive (use that for a 2D spectrum visual instead). Creates a new baseCOMP under. 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 create_3d_audio_reactive: 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.
create_3d_audio_reactive 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 create_3d_audio_reactive 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 create_3d_audio_reactive. 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.
create_3d_audio_reactive 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