create_from_musicxml · Musescore MCP: Risk & Policy

WHAT IT DOES

What create_from_musicxml does on Musescore

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

This tool creates new files on the filesystem, which is a reversible Write operation. The blast radius is medium because an agent could be tricked into creating many files, consuming disk space, or overwriting existing scores, but the operation is reversible (files can be deleted).

From the tool's definition Tool creates and writes a MuseScore .mscz file from MusicXML input (create_from_musicxml). The description states it will 'Convert a MusicXML string into a MuseScore .mscz file', indicating file creation/writing.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_from_musicxml Rate-limited

create_from_musicxml 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": {
    "create_from_musicxml": {
      "limits": [
        {
          "counter": "create_from_musicxml_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 create_from_musicxml

What does the create_from_musicxml tool do? +

Convert a MusicXML string into a MuseScore .mscz file. 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 create_from_musicxml? +

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

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

Can I rate-limit create_from_musicxml? +

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

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

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