Play a simple example sound using SuperCollider OSC.
AI agents invoke play_example_osc 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.
This tool executes an external operation (audio playback via OSC to SuperCollider) whose effects depend on the call. It triggers real-time audio synthesis on the host system, which constitutes executing an external operation rather than merely reading or writing data. Severity is medium as it affects audio output and system resources but has limited blast radius beyond that.
From the tool's definition 'Play a simple example sound using SuperCollider OSC' — triggers external audio synthesis operation via OSC protocol
Documented attack patterns abuse exactly the kind of access play_example_osc 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_example_osc:
{
"version": "1",
"default": "deny",
"tools": {
"play_example_osc": {
"limits": [
{
"counter": "play_example_osc_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}play_example_osc 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 a simple example sound using SuperCollider OSC. 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_example_osc: 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_example_osc 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_example_osc 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_example_osc. 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_example_osc 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.