add_custom_parameters
Append a custom-parameter page (knobs, sliders, toggles, menus, pulses, RGB, XYZ) to a COMP so a generated network becomes a tunable, reusable component. Point
This record as markdown: /tools/io-github-pantani-tdmcp/add-custom-parameters.md
What add_custom_parameters does on tdmcp — TouchDesigner MCP server
AI agents use add_custom_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.
Why add_custom_parameters is rated Medium
This is a Write action: it creates or modifies data (custom parameters on a component) in a way that is reversible—parameters can be removed, adjusted, or reconfigured. It does not delete, destroy, or execute arbitrary code; it simply extends the component's parameter interface.
From the tool's definition Tool appends custom-parameter pages (knobs, sliders, toggles, menus, pulses, RGB, XYZ) to a COMP, which modifies the component's interface and functionality in a reversible, structured manner.
Attacks that exploit this kind of access
The rule that runs add_custom_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 add_custom_parameters, this is the rule to start with:
add_custom_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.
The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every add_custom_parameters call is checked against it from then on.
Questions about add_custom_parameters
Append a custom-parameter page (knobs, sliders, toggles, menus, pulses, RGB, XYZ) to a COMP so a generated network becomes a tunable, reusable component. Point. 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 add_custom_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.
add_custom_parameters 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 add_custom_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.
Set action: deny in the PolicyLayer policy for add_custom_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.
add_custom_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.
More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.
This server
Across the catalogue