This record as markdown: /tools/io-github-kivanccakmak-yaver/storage-upload.md
What storage_upload does on Yaver
AI agents use storage_upload to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | Object key (path) |
file | string | Yes | Local file path |
bucket | string | Yes |
Parameters from the server's own tool schema.
Why storage_upload is rated Medium
This tool writes data to a remote storage system (AWS S3). While not destructive (upload is reversible via deletion), and not financial, it modifies state in a persistent, cloud-based system. The severity is medium because misuse could lead to unauthorized data storage, potential security exposure if sensitive files are uploaded, or resource quota exhaustion—but the blast radius is bounded to storage operations.
From the tool's definition Tool name 'storage_upload' and description 'Upload a file to S3 storage' indicate the tool creates or modifies data in cloud storage by uploading files.
Risk signalsAccepts file system path (file)
Attacks that exploit this kind of access
The rule that runs storage_upload safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For storage_upload, this is the rule to start with:
storage_upload 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 Yaver, apply this rule, and every storage_upload call is checked against it from then on.
Questions about storage_upload
Upload a file to S3 storage. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
storage_upload accepts 3 parameters: key, file, bucket. Required: key, file, bucket. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for storage_upload: 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 Yaver. Nothing to install.
storage_upload 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 storage_upload 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 storage_upload. 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.
storage_upload is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue