Lists the caller's OWN YAFL transfers only — metadata only (id, size, status, expiry, and a download path). Never returns file contents, never a decrypted name, and never another account's files. Optionally cap the number of results with limit.
AI agents call list_files 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 |
|---|---|---|---|
limit | integer | — | Maximum number of transfers to return (most recent first). Omit for the full capped list. |
Parameters from the server's own tool schema.
This tool retrieves metadata about the caller's own file transfers. It has no side effects, does not modify data, and returns only read-only metadata (id, size, status, expiry, download path). The access control ensuring only the caller's own files are visible significantly limits the blast radius of misuse. Severity is low because metadata-only retrieval of one's own data has minimal security impact.
From the tool's definition Tool description states it 'Lists the caller's OWN YAFL transfers only — metadata only (id, size, status, expiry, and a download path)' and explicitly 'Never returns file contents, never a decrypted name, and never another account's files.' This is clearly a…
Attacks that exploit this kind of access
Lists the caller's OWN YAFL transfers only — metadata only (id, size, status, expiry, and a download path). Never returns file contents, never a decrypted name, and never another account's files. Optionally cap the number of results with limit. It is categorised as a Read tool in the Yafldev MCP Server, which means it retrieves data without modifying state.
list_files accepts 1 parameter: limit. 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 list_files: 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.
list_files 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_files 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_files. 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_files 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.
list_files 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 →