AI agents invoke play_synth to trigger actions in SuperCollider OSC MCP. 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.
The tool almost certainly triggers audio synthesis in SuperCollider via OSC, which constitutes executing an external operation. The description is empty, so confidence is reduced, but the server context and naming convention strongly suggest it plays/triggers a synthesizer. No financial, destructive, or write implications are apparent.
From the tool's definition Tool name 'play_synth' on a server that 'controls SuperCollider audio synthesis via OSC'; sibling tools like 'play_melody' and 'play_example_osc' confirm the pattern of triggering external audio operations.
Documented attack patterns abuse exactly the kind of access play_synth gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SuperCollider OSC MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for play_synth:
{
"version": "1",
"default": "deny",
"tools": {
"play_synth": {
"limits": [
{
"counter": "play_synth_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}play_synth 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.
play_synth. It is categorised as a Execute tool in the SuperCollider OSC MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SuperCollider OSC MCP server in PolicyLayer and add a rule for play_synth: 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 SuperCollider OSC MCP. Nothing to install.
play_synth 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 play_synth 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 play_synth. 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.
play_synth is provided by the SuperCollider OSC MCP server (tok/supercollidermcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SuperCollider OSC MCP, 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.
11 SuperCollider OSC MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.