connect_people_counting_bus
Create a people-counting scaffold with aggregate zone counts, sample windows, adapter source, and privacy policy notes.
This record as markdown: /tools/io-github-pantani-tdmcp/connect-people-counting-bus.md
What connect_people_counting_bus does on tdmcp — TouchDesigner MCP server
AI agents use connect_people_counting_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 connect_people_counting_bus is rated Medium
This is a Write operation because it creates new data structures (a scaffold with counts, windows, adapters, and policy notes) within the TouchDesigner project. It does not execute arbitrary code or trigger external operations with unpredictable effects (Execute), does not irreversibly delete data (Destructive), and does not move money (Financial).
From the tool's definition The tool 'connect_people_counting_bus' is described as creating a 'people-counting scaffold with aggregate zone counts, sample windows, adapter source, and privacy policy notes.' The verb 'create' and the concept of building a scaffold structure indicates…
Attacks that exploit this kind of access
The rule that runs connect_people_counting_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 connect_people_counting_bus, this is the rule to start with:
connect_people_counting_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 connect_people_counting_bus call is checked against it from then on.
Questions about connect_people_counting_bus
Create a people-counting scaffold with aggregate zone counts, sample windows, adapter source, and privacy policy notes. 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 connect_people_counting_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.
connect_people_counting_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 connect_people_counting_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 connect_people_counting_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.
connect_people_counting_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