This record as markdown: /tools/io-github-pantani-tdmcp/reload-bridge.md
What reload_bridge does on tdmcp — TouchDesigner MCP server
AI agents invoke reload_bridge 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 reload_bridge is rated High
Hot-reloading a bridge is an active execution operation that restarts or reinitializes a running component. This has side effects (disrupting active connections, resetting state) but is not inherently destructive or financial. It falls under Execute as it triggers an external operational action whose effects depend on the current system state.
From the tool's definition 'Hot-reload the bridge' — triggers a reload/restart operation on the MCP bridge component
Attacks that exploit this kind of access
The rule that runs reload_bridge 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 reload_bridge, this is the rule to start with:
reload_bridge 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 reload_bridge call is checked against it from then on.
Questions about reload_bridge
Hot-reload the bridge. 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 reload_bridge: 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.
reload_bridge 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 reload_bridge 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 reload_bridge. 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.
reload_bridge 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