AI agents invoke send_control_change to trigger actions in MCP MIDI Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation by sending a MIDI CC message to connected software/hardware. It doesn't merely read or write stored data — it actively drives real-time control signals to MIDI-capable systems, which could affect audio equipment, synthesizers, or other software.
From the tool's definition Sends a MIDI Control Change (CC) message
Documented attack patterns abuse exactly the kind of access send_control_change gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP MIDI Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send_control_change:
{
"version": "1",
"default": "deny",
"tools": {
"send_control_change": {
"limits": [
{
"counter": "send_control_change_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}send_control_change stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Sends a MIDI Control Change (CC) message. It is categorised as a Execute tool in the MCP MIDI Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP MIDI Server MCP server in PolicyLayer and add a rule for send_control_change: 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 MCP MIDI Server. Nothing to install.
send_control_change is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_control_change 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 send_control_change. 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.
send_control_change is provided by the MCP MIDI Server MCP server (sandst1/mcp-server-midi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP MIDI Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 MCP MIDI Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.