disconnect_all_midi_cc_from_processor

WHAT IT DOES

What disconnect_all_midi_cc_from_processor does on Sushi MCP Server

AI agents use disconnect_all_midi_cc_from_processor 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.

WHY IT NEEDS A POLICY

Why disconnect_all_midi_cc_from_processor needs a policy

This tool modifies audio configuration state by removing MIDI CC connections, which is a reversible write operation. While it affects multiple connections at once ('all'), the action can be undone by re-establishing the connections. It does not execute arbitrary code, delete data irreversibly, or move financial resources.

From the tool's definition Tool name and description: 'disconnect_all_midi_cc_from_processor' — 'Disconnect all MIDI CC connections from a processor.' This modifies the audio engine configuration by removing MIDI CC routings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disconnect_all_midi_cc_from_processor Rate-limited

disconnect_all_midi_cc_from_processor 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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sushi MCP Server, so you can run agents against it safely.

FAQ

Questions about disconnect_all_midi_cc_from_processor

What does the disconnect_all_midi_cc_from_processor tool do? +

Disconnect all MIDI CC connections from a processor. 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.

How do I enforce a policy on disconnect_all_midi_cc_from_processor? +

Register the Sushi MCP Server MCP server in PolicyLayer and add a rule for disconnect_all_midi_cc_from_processor: 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.

What risk level is disconnect_all_midi_cc_from_processor? +

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

Can I rate-limit disconnect_all_midi_cc_from_processor? +

Yes. Add a rate_limit block to the disconnect_all_midi_cc_from_processor 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 disconnect_all_midi_cc_from_processor completely? +

Set action: deny in the PolicyLayer policy for disconnect_all_midi_cc_from_processor. 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 disconnect_all_midi_cc_from_processor? +

disconnect_all_midi_cc_from_processor 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.