lidar_floor_tracker
Build a floor-occupancy tracker scaffold for synthetic rehearsal, Ouster TOP, Leuze ROD4 CHOP, or UDP point input. Produces a tracked_points CHOP plus a floor preview TOP; hardware modes default inactive and remain explicitly unverified until a real sensor is connected.
This record as markdown: /tools/io-github-pantani-tdmcp/lidar-floor-tracker.md
What lidar_floor_tracker does on tdmcp — TouchDesigner MCP server
AI agents invoke lidar_floor_tracker 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 lidar_floor_tracker is rated High
This tool executes code to construct a visual processing pipeline and orchestrate external hardware interactions (Ouster LiDAR, Leuze ROD4, UDP input). Although hardware connections remain unverified until real sensors attach, the tool itself runs initialization and tracking logic.
From the tool's definition The tool 'builds a floor-occupancy tracker scaffold' and 'produces a tracked_points CHOP plus a floor preview TOP', indicating it executes code that creates and configures visual processing nodes.
Attacks that exploit this kind of access
The rule that runs lidar_floor_tracker 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 lidar_floor_tracker, this is the rule to start with:
lidar_floor_tracker 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 lidar_floor_tracker call is checked against it from then on.
Questions about lidar_floor_tracker
Build a floor-occupancy tracker scaffold for synthetic rehearsal, Ouster TOP, Leuze ROD4 CHOP, or UDP point input. Produces a tracked_points CHOP plus a floor preview TOP; hardware modes default inactive and remain explicitly unverified until a real sensor is connected. 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 lidar_floor_tracker: 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.
lidar_floor_tracker 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 lidar_floor_tracker 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 lidar_floor_tracker. 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.
lidar_floor_tracker 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