AI agents invoke create_sequence 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 server context indicates this tool likely triggers audio synthesis operations in SuperCollider via OSC messages. Based on sibling tools that 'play' or 'create' audio patterns, 'create_sequence' likely executes an audio sequence, making Execute the most appropriate category. Confidence is lowered due to empty description.
From the tool's definition Tool name 'create_sequence' on a server that controls SuperCollider audio synthesis via OSC; sibling tools include play_melody, play_synth, create_drum_pattern, suggesting execution of audio synthesis operations.
Documented attack patterns abuse exactly the kind of access create_sequence 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 create_sequence:
{
"version": "1",
"default": "deny",
"tools": {
"create_sequence": {
"limits": [
{
"counter": "create_sequence_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}create_sequence 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.
create_sequence. 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 create_sequence: 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.
create_sequence 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 create_sequence 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 create_sequence. 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.
create_sequence 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.