convert_score · Musescore MCP: Risk & Policy

WHAT IT DOES

What convert_score does on Musescore

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

Score conversion transforms musical data from one format to another, producing new or modified files. This is reversible (the original file remains) and does not delete data, so it is Write rather than Destructive. It is not Execute because conversion is a data transformation, not arbitrary code execution. No financial or destructive impact.

From the tool's definition Tool name 'convert_score' in a MuseScore MCP server that 'convert, edit, and analyze MuseScore files (.mscz, .musicxml, MIDI)'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

convert_score Rate-limited

convert_score 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": {
    "convert_score": {
      "limits": [
        {
          "counter": "convert_score_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 convert_score

What does the convert_score tool do? +

convert_score. 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 convert_score? +

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

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

Can I rate-limit convert_score? +

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

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

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

// THE FULL RECORD

convert_score is one line of Musescore's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →