update_song · Bandmate MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_song does on Bandmate MCP Server

AI agents use update_song to create or update resources in Bandmate MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bandmate MCP Server environment.

WHY IT NEEDS A POLICY

Why update_song needs a policy

This tool creates or modifies data reversibly, fitting the Write category. It operates on existing songs with targeted field updates rather than destructive deletion. Severity is medium because unauthorized updates could corrupt music metadata or lyrics, but changes are reversible and scoped to individual songs. Confidence is high due to explicit 'Update' language in both name and description.

From the tool's definition Tool name 'update_song' and description 'Update specific fields of an existing song by ID' indicate modification of existing data. The phrase 'Only provided fields are updated' confirms reversible changes to song metadata, chord notations, or lyrics.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_song Rate-limited

update_song 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_song": {
      "limits": [
        {
          "counter": "update_song_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 Bandmate MCP Server, so you can run agents against it safely.

FAQ

Questions about update_song

What does the update_song tool do? +

Update specific fields of an existing song by ID. Only provided fields are updated. Requires authentication. It is categorised as a Write tool in the Bandmate MCP Server 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_song? +

Register the Bandmate MCP Server MCP server in PolicyLayer and add a rule for update_song: 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 Bandmate MCP Server. Nothing to install.

What risk level is update_song? +

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

Can I rate-limit update_song? +

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

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

update_song is provided by the Bandmate MCP Server MCP server (jnicolasgomez/bandmate-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.