sing_over_instrumental · MusicGPT MCP Server MCP

WHAT IT DOES

What sing_over_instrumental does on MusicGPT MCP Server

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

WHY IT NEEDS A POLICY

Why sing_over_instrumental needs a policy

This tool creates or modifies audio content by adding generated vocal elements to an existing track. It produces new audio output without permanently deleting or overwriting the original file (reversible via separate save/upload). The generated content is a derivative work, making this a Write operation rather than Read (which would only analyze) or Execute (which would run arbitrary code).

From the tool's definition Tool name 'sing_over_instrumental' and description 'Add AI-generated vocals over an instrumental track' indicate creation of new audio content by combining/overlaying generated vocals with existing audio.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sing_over_instrumental Rate-limited

sing_over_instrumental 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": {
    "sing_over_instrumental": {
      "limits": [
        {
          "counter": "sing_over_instrumental_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 MusicGPT MCP Server, so you can run agents against it safely.

FAQ

Questions about sing_over_instrumental

What does the sing_over_instrumental tool do? +

Add AI-generated vocals over an instrumental track. It is categorised as a Write tool in the MusicGPT 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 sing_over_instrumental? +

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

What risk level is sing_over_instrumental? +

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

Can I rate-limit sing_over_instrumental? +

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

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

sing_over_instrumental is provided by the MusicGPT MCP Server MCP server (pasie15/mcp-server-musicgpt). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.