Play an audio file. Supports WAV and MP3 formats.
AI agents invoke play_audio 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.
Playing audio is not a simple data read; it triggers an external action (audio playback via system or media player), making it Execute. Misuse could involve playing unwanted or malicious audio content, but the blast radius is limited, hence medium severity.
From the tool's definition "Play an audio file" — triggers an external playback operation whose effect depends on the argument (the audio file path/URL).
Attacks that exploit this kind of access
Play an audio file. Supports WAV and MP3 formats. 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.
Register the Mureka MCP Server MCP server in PolicyLayer and add a rule for play_audio: 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.
play_audio is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the play_audio 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.
Set action: deny in the PolicyLayer policy for play_audio. 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.
play_audio 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.