repair_network
Bounded, autonomous repair: scan cook errors under a subtree, classify each, and plan a safe fix, capped at max_steps so it can never run away. Defaults to dry_run (PLAN only, no changes). Set dry_run:false to apply the known-safe fixes — resetting a broken parameter expression to constant mode, ...
This record as markdown: /tools/io-github-pantani-tdmcp/repair-network.md
What repair_network does on tdmcp — TouchDesigner MCP server
AI agents call repair_network to permanently remove resources in tdmcp — TouchDesigner MCP server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why repair_network is rated Critical
An AI agent that decides to call repair_network doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from tdmcp — TouchDesigner MCP server is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs repair_network 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 repair_network, this is the rule to start with:
repair_network is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every repair_network call is checked against it from then on.
Questions about repair_network
Bounded, autonomous repair: scan cook errors under a subtree, classify each, and plan a safe fix, capped at max_steps so it can never run away. Defaults to dry_run (PLAN only, no changes). Set dry_run:false to apply the known-safe fixes — resetting a broken parameter expression to constant mode, and re-enabling a bypassed/display-off op — within the same bound; risky cases (DAT syntax errors, missing inputs, unclassified errors) are always PLAN-only. Re-checks errors after applying and stops at the bound or when errors clear. Returns {parent_path, dry_run, max_steps, errors_before, errors_after, steps[], remaining[], warnings, rolled_back}. Use it as the diagnostic. It is categorised as a Destructive tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for repair_network: 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.
repair_network is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the repair_network 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 repair_network. 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.
repair_network 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