export_parts · Musescore MCP: Risk & Policy

WHAT IT DOES

What export_parts does on Musescore

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

Based on the 'export_' prefix and the sibling tool 'export_png_pages' which clearly performs output operations, this tool likely creates or writes exported musical parts to disk. While the description is empty, the context of MuseScore file manipulation and the parallel export functionality suggest this creates new files (Write category).

From the tool's definition Tool name 'export_parts' combined with server context showing file conversion and export capabilities (see sibling tools 'export_png_pages', 'convert_score', 'batch_convert'). The 'export_' prefix indicates output/creation of new files.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_parts Rate-limited

export_parts 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": {
    "export_parts": {
      "limits": [
        {
          "counter": "export_parts_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 export_parts

What does the export_parts tool do? +

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

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

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

Can I rate-limit export_parts? +

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

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

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