info

THE RISK

Low Risk

Why info needs a policy

This tool retrieves server status and diagnostic information without modifying any state, executing commands, or affecting music playback or library data. It is a straightforward read operation that poses minimal security risk.

From the tool's definition Tool name 'info' and description 'Get diagnostic information about the Music MCP server status' indicate retrieval of status/diagnostic data with no side effects.

Documented attack patterns abuse exactly the kind of access info gives an agent:

POLICY

How to control info

PolicyLayer is an MCP gateway — it sits between your AI agents and Music MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "info": {}
  }
}

info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Music MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Music MCP tools

Execute execute_music_command Execute music playback control commands Execute queue_music Manage music queue and enhanced playlist control Write manage_playlist Create and manage playlists Read get_music_info Retrieve information about current playback or library Read search_music Search the music library

All 6 Music MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about info

What does the info tool do? +

Get diagnostic information about the Music MCP server status. It is categorised as a Read tool in the Music MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on info? +

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

What risk level is info? +

info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit info? +

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

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

info is provided by the Music MCP server (pedrocid/music-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Music MCP tool call.

Start from Music MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →