Play an informational system sound
AI agents invoke play_info_sound to trigger actions in MCP Make Sound. 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.
This tool executes a system-level action (playing a sound) that produces a real-world side effect (audio output). It doesn't read, write, or delete data, but it does trigger an external operation. Severity is low since the blast radius of playing an informational sound is minimal.
From the tool's definition "Play an informational system sound" — triggers an external audio operation on the host system
Attacks that exploit this kind of access
Play an informational system sound. It is categorised as a Execute tool in the MCP Make Sound MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Make Sound MCP server in PolicyLayer and add a rule for play_info_sound: 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 MCP Make Sound. Nothing to install.
play_info_sound 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_info_sound 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_info_sound. 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_info_sound is provided by the MCP Make Sound MCP server (nocoo/mcp-make-sound). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →