update_td_node_parameters

SERVERtdmcp — TouchDesigner MCP server SOURCE@dpantani/tdmcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pantani-tdmcp/update-td-node-parameters.md

WHAT IT DOES

What update_td_node_parameters does on tdmcp — TouchDesigner MCP server

AI agents use update_td_node_parameters 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.

RISK

Why update_td_node_parameters is rated Medium

The tool modifies node parameters in a TouchDesigner project, which is a reversible change (parameters can be updated again to different values). This fits the Write category—it creates or modifies data reversibly. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or trigger external operations with unpredictable side effects (Execute).

From the tool's definition Tool description states it 'Modify an existing node by setting one or more of its parameters to constant values' and 'returns the updated {node}'. This is a create/modify operation that changes data in the TouchDesigner project.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_td_node_parameters 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 update_td_node_parameters, this is the rule to start with:

update_td_node_parameters Rate-limited

update_td_node_parameters 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_td_node_parameters": {
      "limits": [
        {
          "counter": "update_td_node_parameters_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every update_td_node_parameters call is checked against it from then on.

FAQ

Questions about update_td_node_parameters

What does the update_td_node_parameters tool do? +

Modify an existing node by setting one or more of its parameters to constant values. The update is strict (not best-effort): an unknown parameter name fails the whole call atomically without changing anything, and a bad value (wrong type or out of range) returns an error naming which parameters applied and which failed. On success returns the updated {node}. To inspect valid parameter names/current values first use get_td_node_parameters; to make a parameter move over time use animate_parameter instead of a static value. 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.

How do I enforce a policy on update_td_node_parameters? +

Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for update_td_node_parameters: 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.

What risk level is update_td_node_parameters? +

update_td_node_parameters is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_td_node_parameters? +

Yes. Add a rate_limit block to the update_td_node_parameters 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.

How do I block update_td_node_parameters completely? +

Set action: deny in the PolicyLayer policy for update_td_node_parameters. 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.

What MCP server provides update_td_node_parameters? +

update_td_node_parameters 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.

KEEP EXPLORING

More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.

This server

All 334 tdmcp — TouchDesigner MCP server tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →