generate_music · Media MCP: Risk & Policy

WHAT IT DOES

What generate_music does on Media

AI agents invoke generate_music to trigger actions in Media. 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_music needs a policy

This tool triggers an external AI model (Google's Lyria) to generate media content. It executes an external operation whose effects depend on the provided prompts. No data is merely read, and it doesn't delete or move money — it invokes a generative AI service to produce output, placing it in the Execute category.

From the tool's definition Generate instrumental music from weighted text prompts using Google's Lyria model

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_music Rate-limited

generate_music 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_music": {
      "limits": [
        {
          "counter": "generate_music_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 Media, so you can run agents against it safely.

FAQ

Questions about generate_music

What does the generate_music tool do? +

Generate instrumental music from weighted text prompts using Google's Lyria model. It is categorised as a Execute tool in the Media 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_music? +

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

What risk level is generate_music? +

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

Can I rate-limit generate_music? +

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

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

generate_music is provided by the Media MCP server (lukaskellerstein/media-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.