transpose_by_key · Musescore MCP: Risk & Policy

WHAT IT DOES

What transpose_by_key does on Musescore

AI agents use transpose_by_key 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_by_key needs a policy

Transposition modifies a MuseScore file by shifting all notes up or down, reversibly changing the musical content. This is a Write operation (modifies data) rather than Execute or Destructive because the change can be undone and does not irreversibly destroy data.

From the tool's definition Tool name 'transpose_by_key' and sibling tools like 'change_tempo', 'change_time_signature', and 'apply_style' that modify MuseScore files. The server description states it 'edit[s]' files, and transposition modifies musical scores.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transpose_by_key Rate-limited

transpose_by_key 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_by_key": {
      "limits": [
        {
          "counter": "transpose_by_key_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_by_key

What does the transpose_by_key tool do? +

transpose_by_key. 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_by_key? +

Register the Musescore MCP server in PolicyLayer and add a rule for transpose_by_key: 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_by_key? +

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

Can I rate-limit transpose_by_key? +

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

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

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