files.extend_file
Extend retention for a file that was uploaded with files.upload_file and appears in files.list_uploaded_files with retained_until. Adds additional_retention_days to the current schedule (or from now if retention already expired). Only files with a completed upload session and retention metadata c...
This record as markdown: /tools/io-github-vee3io-vee3/files.extend-file.md
What files.extend_file does on Vee3
AI agents use files.extend_file 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 |
|---|---|---|---|
file_name | string | Yes | Relative file name or path to extend. Use files.list_uploaded_files and choose a file that includes retained_until. |
additional_retention_days | integer | Yes | Days to add to the file's retention schedule. |
Parameters from the server's own tool schema.
Why files.extend_file is rated Medium
Modifies file retention metadata reversibly; no data deletion or financial transaction involved.
From the tool's definition Extend retention for a file, adds additional_retention_days to current schedule
Attacks that exploit this kind of access
The rule that runs files.extend_file 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.extend_file, this is the rule to start with:
files.extend_file 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.extend_file call is checked against it from then on.
Questions about files.extend_file
Extend retention for a file that was uploaded with files.upload_file and appears in files.list_uploaded_files with retained_until. Adds additional_retention_days to the current schedule (or from now if retention already expired). Only files with a completed upload session and retention metadata can be extended. Cost = max(1, ceil(size_gibibytes * additional_retention_days * 2)) 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.extend_file accepts 2 parameters: file_name, additional_retention_days. Required: file_name, additional_retention_days. 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.extend_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 Vee3. Nothing to install.
files.extend_file 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.extend_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 files.extend_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.
files.extend_file 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