Get the current folder path where downloads are being saved
AI agents call get_current_download_path to retrieve information from MCP YouTube-DLP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and returns the current download directory path—a read-only query with no side effects. It does not download, execute, modify, or delete any data. The low severity reflects minimal risk: knowledge of a folder path alone poses no direct threat even if disclosed or queried repeatedly by an AI agent.
From the tool's definition Tool name 'get_current_download_path' and description 'Get the current folder path where downloads are being saved' indicate a pure query operation that retrieves configuration/state information without modifying anything.
Documented attack patterns abuse exactly the kind of access get_current_download_path gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP YouTube-DLP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_download_path:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_download_path": {}
}
}get_current_download_path is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current folder path where downloads are being saved. It is categorised as a Read tool in the MCP YouTube-DLP MCP Server, which means it retrieves data without modifying state.
Register the MCP YouTube-DLP MCP server in PolicyLayer and add a rule for get_current_download_path: 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 YouTube-DLP. Nothing to install.
get_current_download_path 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 get_current_download_path 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 get_current_download_path. 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.
get_current_download_path is provided by the MCP YouTube-DLP MCP server (yorickchan/mcp_youtube_dlp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP YouTube-DLP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 MCP YouTube-DLP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.