manage_component_storage

What manage_component_storage does on tdmcp — TouchDesigner MCP server

AI agents use manage_component_storage 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_component_storage is rated Medium

CRUD operations typically involve both read and write functionality. However, since Delete is included in the acronym, this could potentially be Destructive. In TouchDesigner's visual/node-based context, component deletion is often reversible (undo available), and the tool name emphasizes 'manage' rather than 'destroy', suggesting the primary intent is data manipulation rather than irreversible destruction.

From the tool's definition Tool description states 'CRUD operations on a COMP operator' — Create, Read, Update, Delete. While CRUD spans multiple categories, the emphasis on 'manage' and 'storage' in the context of a visual design tool (TouchDesigner) suggests primarily reversible…

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

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

Questions about manage_component_storage