connect_midi_mpe_controller
Create an expressive MIDI MPE input/output scaffold with zone and expression maps for pressure, timbre, pitch bend, and note channels.
This record as markdown: /tools/io-github-pantani-tdmcp/connect-midi-mpe-controller.md
What connect_midi_mpe_controller does on tdmcp — TouchDesigner MCP server
AI agents use connect_midi_mpe_controller 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 connect_midi_mpe_controller is rated Medium
This tool modifies TouchDesigner project state by creating new MIDI MPE controller mappings and configuration structures. While it does not execute external code or delete data, it substantively alters the project's MIDI routing and parameter bindings, which classifies it as Write.
From the tool's definition Tool creates/modifies MIDI input/output scaffold configuration including zone and expression maps. Described actions are 'Create' (reversible configuration change) affecting MIDI controller bindings and parameters.
Attacks that exploit this kind of access
The rule that runs connect_midi_mpe_controller 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 connect_midi_mpe_controller, this is the rule to start with:
connect_midi_mpe_controller 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 connect_midi_mpe_controller call is checked against it from then on.
Questions about connect_midi_mpe_controller
Create an expressive MIDI MPE input/output scaffold with zone and expression maps for pressure, timbre, pitch bend, and note channels. 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 connect_midi_mpe_controller: 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.
connect_midi_mpe_controller 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 connect_midi_mpe_controller 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 connect_midi_mpe_controller. 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.
connect_midi_mpe_controller 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