build_sop_geometry
Declarative Layer-2 builder for an ordered SOP geometry chain. Pass an
This record as markdown: /tools/io-github-pantani-tdmcp/build-sop-geometry.md
What build_sop_geometry does on tdmcp — TouchDesigner MCP server
AI agents invoke build_sop_geometry 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 build_sop_geometry is rated High
This tool triggers execution of a geometry processing pipeline whose side effects (visual output, computational state changes in the TouchDesigner project) depend entirely on the arguments passed. While not destructive to persistent data, it executes external operations (SOP chain evaluation) and modifies the live project state, placing it in the Execute category.
From the tool's definition 'Declarative Layer-2 builder for an ordered SOP geometry chain' — constructs and configures a procedural geometry pipeline in TouchDesigner.
Attacks that exploit this kind of access
The rule that runs build_sop_geometry 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 build_sop_geometry, this is the rule to start with:
build_sop_geometry 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.
The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every build_sop_geometry call is checked against it from then on.
Questions about build_sop_geometry
Declarative Layer-2 builder for an ordered SOP geometry chain. Pass an. 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.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for build_sop_geometry: 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.
build_sop_geometry 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 build_sop_geometry 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 build_sop_geometry. 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.
build_sop_geometry 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.
Across the catalogue