manage_presets

Store, recall, list, or delete named snapshots of a COMP

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/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).

Questions about manage_presets

What does the manage_presets tool do? +

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.

How do I enforce a policy on manage_presets? +

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.

What risk level is manage_presets? +

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

Can I rate-limit manage_presets? +

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.

How do I block manage_presets completely? +

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.

What MCP server provides manage_presets? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of tdmcp — TouchDesigner MCP server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.