transpose_for_instrument · Musescore MCP: Risk & Policy

WHAT IT DOES

What transpose_for_instrument does on Musescore

AI agents use transpose_for_instrument to create or update resources in Musescore — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Musescore environment.

WHY IT NEEDS A POLICY

Why transpose_for_instrument needs a policy

Transposition is a reversible modification to musical scores—it changes pitch relationships but does not delete or destroy data. This aligns with the Write category (creates or modifies data reversibly). Severity is medium because misuse could corrupt a user's musical composition, but the change is undoable.

From the tool's definition Tool name 'transpose_for_instrument' and server description stating it supports 'transposition' as a core capability. The server enables 'edit' operations on MuseScore files (.mscz, .musicxml, MIDI). Transposition modifies musical content reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transpose_for_instrument Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Musescore, so you can run agents against it safely.

FAQ

Questions about transpose_for_instrument

What does the transpose_for_instrument tool do? +

transpose_for_instrument. It is categorised as a Write tool in the Musescore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on transpose_for_instrument? +

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

What risk level is transpose_for_instrument? +

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

Can I rate-limit transpose_for_instrument? +

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

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

transpose_for_instrument is provided by the Musescore MCP server (strongbeen04/musescore-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.