This record as markdown: /tools/4shil-ytm-mcp/download-history.md
What download_history does on Ytm
AI agents call download_history 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 download_history is rated Low
This tool queries and exports user listening history data. It has no side effects on the system or user data — it does not modify playlists, delete history, execute playback, or commit financial transactions. The retrieval of metadata about past listening is a read operation with minimal blast radius.
From the tool's definition Tool description states 'Download last N songs from listening history' — this retrieves historical listening data without modifying or deleting it. The word 'download' here means export/retrieve, not execute code or trigger playback actions.
Attacks that exploit this kind of access
The rule that runs download_history 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 download_history, this is the rule to start with:
download_history 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 download_history call is checked against it from then on.
Questions about download_history
Download last N songs from listening history. 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 download_history: 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.
download_history 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 download_history 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 download_history. 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.
download_history 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