update_metadata · Musescore MCP: Risk & Policy

WHAT IT DOES

What update_metadata does on Musescore

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

The tool performs a modification operation on file metadata, which is reversible and has limited blast radius compared to destructive or financial operations. This aligns with the Write category. Severity is medium because modifying metadata could affect file attribution, searchability, or integrity, but the changes are not destructive and not financial in nature.

From the tool's definition Tool name 'update_metadata' indicates modification of file metadata. The server description confirms the tool operates on MuseScore files (.mscz, .musicxml, MIDI).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_metadata Rate-limited

update_metadata 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": {
    "update_metadata": {
      "limits": [
        {
          "counter": "update_metadata_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 update_metadata

What does the update_metadata tool do? +

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

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

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

Can I rate-limit update_metadata? +

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

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

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