files.list_uploaded_files
List files currently stored for the authenticated Vee3 account. Returns file_name (including any folders), content_type, size_bytes, uploaded_at, and retained_until when known. Use file_name to reference a file in other capabilities. Optional folder limits results to that folder path and its subf...
This record as markdown: /tools/io-github-vee3io-vee3/files.list-uploaded-files.md
What files.list_uploaded_files does on Vee3
AI agents use files.list_uploaded_files to create or update resources in Vee3, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vee3 environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
folder | object | — | Optional folder path (for example media/clips). When set, only files under that folder (including nested subfolders) are returned. Do not use '..' or absolute p |
Parameters from the server's own tool schema.
Why files.list_uploaded_files is rated Medium
An AI agent can call files.list_uploaded_files faster than any human can review: one bad instruction and it creates or modifies resources in Vee3 by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (folder)
Attacks that exploit this kind of access
The rule that runs files.list_uploaded_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For files.list_uploaded_files, this is the rule to start with:
files.list_uploaded_files stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every files.list_uploaded_files call is checked against it from then on.
Questions about files.list_uploaded_files
List files currently stored for the authenticated Vee3 account. Returns file_name (including any folders), content_type, size_bytes, uploaded_at, and retained_until when known. Use file_name to reference a file in other capabilities. Optional folder limits results to that folder path and its subfolders (for example media/clips). retained_until is when the file will be removed (based on retention_days at upload). Cost = 0 tokens. It is categorised as a Write tool in the Vee3 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
files.list_uploaded_files accepts 1 parameter: folder. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for files.list_uploaded_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 Vee3. Nothing to install.
files.list_uploaded_files is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the files.list_uploaded_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 files.list_uploaded_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.
files.list_uploaded_files is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue