connect_ticketing_checkin_bus
Create a ticketing/check-in scaffold with aggregate gate counts, ticket-tier maps, gate status, adapter source, and PII/token safety notes.
This record as markdown: /tools/io-github-pantani-tdmcp/connect-ticketing-checkin-bus.md
What connect_ticketing_checkin_bus does on tdmcp — TouchDesigner MCP server
AI agents use connect_ticketing_checkin_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_ticketing_checkin_bus is rated Medium
This tool creates new data structures (scaffold with gate counts, ticket-tier maps, gate status, etc.) and explicitly handles PII/tokens, making it a Write-category tool. The mention of PII/token safety notes elevates severity from low to medium due to the sensitive nature of personal and authentication data involved, though no irreversible deletion or financial transactions are indicated.
From the tool's definition Tool description states 'Create a ticketing/check-in scaffold' — the verb 'create' indicates data generation/modification. Manages sensitive data (PII/token safety notes mentioned explicitly) in a ticketing system context.
Attacks that exploit this kind of access
The rule that runs connect_ticketing_checkin_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_ticketing_checkin_bus, this is the rule to start with:
connect_ticketing_checkin_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_ticketing_checkin_bus call is checked against it from then on.
Questions about connect_ticketing_checkin_bus
Create a ticketing/check-in scaffold with aggregate gate counts, ticket-tier maps, gate status, adapter source, and PII/token safety 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_ticketing_checkin_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_ticketing_checkin_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_ticketing_checkin_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_ticketing_checkin_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_ticketing_checkin_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