Downloads and decrypts exactly the one file referenced by the given YAFL share url, writing it only into destDir (default: the current working directory) — never anywhere else. Requires the decryption key embedded in the URL fragment; the key is used only locally to decrypt and is never sent to t...
AI agents call download_file to retrieve information from Yafldev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | A YAFL share URL including the fragment key, e.g. https://yafl.dev/t/{id}#{key} |
destDir | string | — | Directory to write the downloaded file into (absolute or cwd-relative); defaults to the current working directory. The file is written only inside this director |
password | string | — | Password for a password-protected (v2) link. Used only locally to derive the decryption key — never sent to the API. Required when the link is password-protecte |
Parameters from the server's own tool schema.
This tool retrieves encrypted file data from a remote source and decrypts it locally. While it does write to the filesystem, this is an inherent side effect of the download operation itself, not a modification of existing data. The tool has no capability to create, modify existing files, delete, or execute arbitrary code.
From the tool's definition Tool description states it 'Downloads and decrypts exactly the one file referenced by the given YAFL share url, writing it only into destDir'. The primary action is downloading/retrieving data with decryption applied locally.
Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (password)
Attacks that exploit this kind of access
Downloads and decrypts exactly the one file referenced by the given YAFL share url, writing it only into destDir (default: the current working directory) — never anywhere else. Requires the decryption key embedded in the URL fragment; the key is used only locally to decrypt and is never sent to the API. It is categorised as a Read tool in the Yafldev MCP Server, which means it retrieves data without modifying state.
download_file accepts 3 parameters: url, destDir, password. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Yafldev MCP server in PolicyLayer and add a rule for download_file: 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 Yafldev. Nothing to install.
download_file 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_file 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_file. 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_file is provided by the Yafldev MCP server (@yafldev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
download_file is one line of Yafldev's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →