set_live_tempo

THE RISK

Medium Risk

Why set_live_tempo needs a policy

Setting the tempo modifies the score's metadata/playback properties. This is a reversible write operation (tempo can be changed again), affecting a live music score. Misuse could disrupt a live performance session but is not destructive or financial in nature.

From the tool's definition 'Set the tempo in the live score' — modifies a property of an existing score

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

POLICY

How to control set_live_tempo

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_live_tempo": {
      "limits": [
        {
          "counter": "set_live_tempo_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

set_live_tempo stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Mcp Score — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mcp Score tools

Write add_live_chord_symbol Add a chord symbol in the live score. Write add_live_rehearsal_mark Add a rehearsal mark in the live score. Write disconnect_from_dorico Disconnect from Dorico. Write disconnect_from_musescore Disconnect from MuseScore. Write set_live_barline Set a barline type in the live score. Write set_live_key_signature Set the key signature in the live score. Write transpose_passage transpose_passage Write undo_last_action Undo the last action in the connected score application.

All 18 Mcp Score tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about set_live_tempo

What does the set_live_tempo tool do? +

Set the tempo in the live score. It is categorised as a Write tool in the Mcp Score MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_live_tempo? +

Register the Mcp Score MCP server in PolicyLayer and add a rule for set_live_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 Mcp Score. Nothing to install.

What risk level is set_live_tempo? +

set_live_tempo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_live_tempo? +

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

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

set_live_tempo is provided by the Mcp Score MCP server (tskovlund/mcp-score). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Score tool call.

Start from Mcp Score, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →