Disconnect a MIDI CC from a parameter.
AI agents use disconnect_midi_cc to create or update resources in Sushi MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sushi MCP Server environment.
This tool modifies system configuration reversibly by disconnecting MIDI control routing. It does not permanently delete data (the mapping can be re-established), does not execute arbitrary code, and does not move financial assets. The action is reversible, placing it in the Write category.
From the tool's definition Tool name is 'disconnect_midi_cc' and description states it 'Disconnect a MIDI CC from a parameter.' This modifies MIDI routing configuration by removing a connection between a control change message and an audio parameter.
Attacks that exploit this kind of access
Disconnect a MIDI CC from a parameter. It is categorised as a Write tool in the Sushi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sushi MCP Server MCP server in PolicyLayer and add a rule for disconnect_midi_cc: 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 Sushi MCP Server. Nothing to install.
disconnect_midi_cc 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 disconnect_midi_cc 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 disconnect_midi_cc. 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.
disconnect_midi_cc is provided by the Sushi MCP Server MCP server (nagarjun226/sushi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →