This record as markdown: /tools/4shil-ytm-mcp/list-downloads.md
What list_downloads does on Ytm
AI agents call list_downloads to retrieve information from Ytm without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_downloads is rated Low
This tool queries and returns information about previously downloaded songs without creating, modifying, deleting, or executing any operations. It is a straightforward read-only action that presents stored data to the user. The blast radius of misuse is minimal, as an AI agent listing downloads cannot cause harm beyond accessing metadata about the user's media library.
From the tool's definition Tool name is 'list_downloads' and description states 'List all downloaded songs' — purely a retrieval operation with no modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs list_downloads safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ytm, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_downloads, this is the rule to start with:
list_downloads is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ytm, apply this rule, and every list_downloads call is checked against it from then on.
Questions about list_downloads
List all downloaded songs. It is categorised as a Read tool in the Ytm MCP Server, which means it retrieves data without modifying state.
Register the Ytm MCP server in PolicyLayer and add a rule for list_downloads: 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 Ytm. Nothing to install.
list_downloads 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_downloads 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_downloads. 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_downloads is provided by the Ytm MCP server (4shil/ytm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ytm, and thousands of servers like it.
This server
Across the catalogue