generate_instrumental · Mureka MCP Server MCP: Risk & Policy

WHAT IT DOES

What generate_instrumental does on Mureka MCP Server

AI agents invoke generate_instrumental to trigger actions in Mureka MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why generate_instrumental needs a policy

Based on the server context (generating music/audio via external APIs) and the tool name, this tool likely triggers an external API call to generate instrumental music. This is an Execute-category action as it invokes an external operation. Confidence is reduced due to the empty description. Severity is medium as misuse could consume API credits or generate unwanted content, but blast radius is limited.

From the tool's definition Tool name 'generate_instrumental' on a server described as enabling generation of songs and background music through Mureka's APIs; description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_instrumental Rate-limited

generate_instrumental stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_instrumental": {
      "limits": [
        {
          "counter": "generate_instrumental_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mureka MCP Server, so you can run agents against it safely.

FAQ

Questions about generate_instrumental

What does the generate_instrumental tool do? +

generate_instrumental. It is categorised as a Execute tool in the Mureka MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on generate_instrumental? +

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

What risk level is generate_instrumental? +

generate_instrumental is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit generate_instrumental? +

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

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

generate_instrumental is provided by the Mureka MCP Server MCP server (skyworkai/mureka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.