manage_presets
Store, recall, list, or delete named snapshots of a COMP
This record as markdown: /tools/io-github-pantani-tdmcp/manage-presets.md
What manage_presets does on tdmcp — TouchDesigner MCP server
AI agents use manage_presets 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 manage_presets is rated Medium
The tool primarily manages snapshots—storing and recalling are Write operations (reversible state changes). Deletion of presets is destructive in isolation, but since the tool bundles multiple operations and snapshots are typically non-critical state data in a visual design context, this is classified as Write rather than Destructive.
From the tool's definition Tool description states 'Store, recall, list, or delete named snapshots of a COMP'. The store, recall, and list operations are reversible modifications (Write category).
Attacks that exploit this kind of access
The rule that runs manage_presets 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 manage_presets, this is the rule to start with:
manage_presets 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 manage_presets call is checked against it from then on.
Questions about manage_presets
Store, recall, list, or delete named snapshots of a COMP. 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 manage_presets: 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.
manage_presets 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 manage_presets 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 manage_presets. 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.
manage_presets 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