create_window_output_matrix
Create a Window COMP output matrix scaffold with window maps, source maps, status, and setup notes.
This record as markdown: /tools/io-github-pantani-tdmcp/create-window-output-matrix.md
What create_window_output_matrix does on tdmcp — TouchDesigner MCP server
AI agents use create_window_output_matrix 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 create_window_output_matrix is rated Medium
This tool generates new visual/structural components (window COMP configurations) within a TouchDesigner project. It is reversible (the created matrix/scaffold can be deleted or modified), so it qualifies as Write rather than Destructive. The blast radius is medium because misconfigured window matrices could affect display output or require rework, but no permanent data loss or financial impact occurs.
From the tool's definition Tool creates a Window COMP output matrix scaffold with window maps, source maps, status, and setup notes. The verb 'Create' and the construction of a 'scaffold' structure indicates data/configuration creation within TouchDesigner.
Attacks that exploit this kind of access
The rule that runs create_window_output_matrix 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 create_window_output_matrix, this is the rule to start with:
create_window_output_matrix 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 create_window_output_matrix call is checked against it from then on.
Questions about create_window_output_matrix
Create a Window COMP output matrix scaffold with window maps, source maps, status, and setup notes. 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 create_window_output_matrix: 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.
create_window_output_matrix 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 create_window_output_matrix 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 create_window_output_matrix. 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.
create_window_output_matrix 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