List all previously generated sound effect files.
AI agents call list_generated_sounds to retrieve information from AudioGen MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing audio generation artifacts without modifying, deleting, or executing operations. It is purely informational. Severity is low because listing local audio files poses minimal risk even if accessed by an untrusted agent—the blast radius is limited to information disclosure of filenames/metadata the user already generated.
From the tool's definition Tool name 'list_generated_sounds' and description 'List all previously generated sound effect files' indicate a retrieval operation with no side effects. The verb 'list' is explicitly a Read operation per the classification rules.
Attacks that exploit this kind of access
List all previously generated sound effect files. It is categorised as a Read tool in the AudioGen MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AudioGen MCP Server MCP server in PolicyLayer and add a rule for list_generated_sounds: 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 AudioGen MCP Server. Nothing to install.
list_generated_sounds is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_generated_sounds 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 list_generated_sounds. 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.
list_generated_sounds is provided by the AudioGen MCP Server MCP server (peerjakobsen/audiogen-mcp). 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 →