AI agents call list_generated_sounds to retrieve information from Portals without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Filter by sound type. Omit to list all types. |
Parameters from the server's own tool schema.
This is a straightforward data retrieval tool that queries and lists sound metadata for the current user. It has no side effects, does not execute code or external operations, does not create or modify data, and does not delete anything. The optional 'type' filter parameter is a standard query parameter for refining results.
From the tool's definition Tool description states 'List AI-generated sounds' and 'Returns sound metadata' — these are query/retrieval operations with no modification of data.
Attacks that exploit this kind of access
List AI-generated sounds (speech, sound effects, music) for the current user. Returns sound metadata including URLs, prompts, and creation dates. Pass type to filter by category. It is categorised as a Read tool in the Portals MCP Server, which means it retrieves data without modifying state.
list_generated_sounds accepts 1 parameter: type. The full parameter table on this page comes from the server's own tool schema.
Register the Portals 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 Portals. 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 Portals MCP server (portals-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 →