High Risk →

set_tempo

Set BPM

How to control set_tempo ↓

AI agents invoke set_tempo to trigger actions in Strudel MCP 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.

High Risk

Setting the BPM in a live coding/music generation environment triggers an external operation through browser automation that affects the running audio engine. It is not a simple data write — it executes a state change in an external browser-controlled application.

From the tool's definition 'Set BPM' — sets the tempo in a live coding environment controlled via browser automation, triggering an external operation that changes playback state in Strudel.cc

Documented attack patterns abuse exactly the kind of access set_tempo gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Strudel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for set_tempo:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_tempo": {
      "limits": [
        {
          "counter": "set_tempo_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Strudel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the set_tempo tool do? +

Set BPM. It is categorised as a Execute tool in the Strudel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on set_tempo? +

Register the Strudel MCP Server MCP server in PolicyLayer and add a rule for set_tempo: 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 Strudel MCP Server. Nothing to install.

What risk level is set_tempo? +

set_tempo is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit set_tempo? +

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

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

set_tempo is provided by the Strudel MCP Server MCP server (williamzujkowski/live-coding-music-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Strudel MCP Server tool call.

Deterministic rules across all 10 Strudel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

10 Strudel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.