connect_mqtt_iot_bus
Create an MQTT Client DAT bus scaffold for IoT sensors, installation telemetry, and policy-gated operator commands.
This record as markdown: /tools/io-github-pantani-tdmcp/connect-mqtt-iot-bus.md
What connect_mqtt_iot_bus does on tdmcp — TouchDesigner MCP server
AI agents invoke connect_mqtt_iot_bus 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 connect_mqtt_iot_bus is rated High
This tool does more than write configuration data; it creates a live MQTT client connection that subscribes/publishes to an IoT message bus and can receive 'operator commands'. This constitutes executing an external network operation with ongoing side effects.
From the tool's definition 'Create an MQTT Client DAT bus scaffold' and 'policy-gated operator commands' — establishes an active network connection and communication bus that can receive and trigger operator commands from external IoT sources
Attacks that exploit this kind of access
The rule that runs connect_mqtt_iot_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_mqtt_iot_bus, this is the rule to start with:
connect_mqtt_iot_bus 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 connect_mqtt_iot_bus call is checked against it from then on.
Questions about connect_mqtt_iot_bus
Create an MQTT Client DAT bus scaffold for IoT sensors, installation telemetry, and policy-gated operator commands. 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 connect_mqtt_iot_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_mqtt_iot_bus 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 connect_mqtt_iot_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_mqtt_iot_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_mqtt_iot_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.
Across the catalogue