create_zed_depth_bus
Create a ZED camera depth/body/point-cloud scaffold with ZED TOP/CHOP/SOP placeholders and runtime-gated warnings.
This record as markdown: /tools/io-github-pantani-tdmcp/create-zed-depth-bus.md
What create_zed_depth_bus does on tdmcp — TouchDesigner MCP server
AI agents use create_zed_depth_bus 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_zed_depth_bus is rated Medium
This tool creates new operator nodes (TOP/CHOP/SOP placeholders) and scaffold structures within a TouchDesigner project. It is a Write operation as it adds new components to the project graph. It does not execute code, delete data, or involve financial transactions. Severity is medium because miscreation of nodes could disrupt a live visual system, but changes are reversible.
From the tool's definition 'Create a ZED camera depth/body/point-cloud scaffold' — creates new nodes/placeholders in a TouchDesigner project
Attacks that exploit this kind of access
The rule that runs create_zed_depth_bus 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_zed_depth_bus, this is the rule to start with:
create_zed_depth_bus 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_zed_depth_bus call is checked against it from then on.
Questions about create_zed_depth_bus
Create a ZED camera depth/body/point-cloud scaffold with ZED TOP/CHOP/SOP placeholders and runtime-gated warnings. 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_zed_depth_bus: 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_zed_depth_bus 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_zed_depth_bus 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_zed_depth_bus. 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_zed_depth_bus 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