create_ncam_camera_tracking_bus
Create an NCAM camera-tracking scaffold with pose, lens, video-preview, and calibration maps.
This record as markdown: /tools/io-github-pantani-tdmcp/create-ncam-camera-tracking-bus.md
What create_ncam_camera_tracking_bus does on tdmcp — TouchDesigner MCP server
AI agents use create_ncam_camera_tracking_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_ncam_camera_tracking_bus is rated Medium
The tool creates new components and configurations (scaffold, maps, preview elements) within a TouchDesigner project. This is a Write operation because it creates new, reversible objects and settings. Severity is medium because misconfiguration could require recalibration or rebuild of the tracking system, but doesn't irreversibly delete data, execute arbitrary code, or cause financial impact.
From the tool's definition Tool creates and sets up a camera tracking system ('Create an NCAM camera-tracking scaffold with pose, lens, video-preview, and calibration maps'). This involves creating new data structures and configurations within TouchDesigner that persist in the project.
Attacks that exploit this kind of access
The rule that runs create_ncam_camera_tracking_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_ncam_camera_tracking_bus, this is the rule to start with:
create_ncam_camera_tracking_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_ncam_camera_tracking_bus call is checked against it from then on.
Questions about create_ncam_camera_tracking_bus
Create an NCAM camera-tracking scaffold with pose, lens, video-preview, and calibration maps. 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_ncam_camera_tracking_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_ncam_camera_tracking_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_ncam_camera_tracking_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_ncam_camera_tracking_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_ncam_camera_tracking_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