connect_public_alerts_bus
Create a public-alert scaffold with advisory alert rows, severity maps, routing policy, adapter source, and safety/escalation notes.
This record as markdown: /tools/io-github-pantani-tdmcp/connect-public-alerts-bus.md
What connect_public_alerts_bus does on tdmcp — TouchDesigner MCP server
AI agents use connect_public_alerts_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_public_alerts_bus is rated Medium
This tool creates a new alert system scaffold and configuration within TouchDesigner, which is a reversible modification operation. While it sets up alerting infrastructure that could potentially affect downstream systems or visibility, the action itself is creating/initializing configuration data rather than executing external operations, triggering destructive deletions, or moving resources.
From the tool's definition Tool description states it will 'Create a public-alert scaffold' with multiple components (alert rows, severity maps, routing policy, adapter source, safety/escalation notes). The verb 'Create' and the structured data being instantiated indicate data creation.
Attacks that exploit this kind of access
The rule that runs connect_public_alerts_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_public_alerts_bus, this is the rule to start with:
connect_public_alerts_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_public_alerts_bus call is checked against it from then on.
Questions about connect_public_alerts_bus
Create a public-alert scaffold with advisory alert rows, severity maps, routing policy, adapter source, and safety/escalation 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_public_alerts_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_public_alerts_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_public_alerts_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_public_alerts_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_public_alerts_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