What AI clients can do
The six quickS3 tools an AI client can use, the permission each one needs, and everything an AI client is not able to do with your files.
An AI client connected to quickS3 has six tools. That’s everything it can do: it can’t delete, rename, move, or create folders, and it can’t touch people, roles, connections, or settings.
| Tool | What it does | Needs |
|---|---|---|
list_connections | Lists the storage connections the client can use. | Read somewhere on the connection |
list_buckets | Lists the buckets on one connection. | Read somewhere in the bucket |
list_objects | Lists files and folders in a bucket, 100 at a time by default and up to 500. | Read |
create_download_link | Makes a download link that works once, for 5 minutes. | Read |
create_share_link | Makes a public link anyone can download from, lasting 5 minutes to 30 days (24 hours by default). | Read |
create_upload_url | Makes an upload link that works for 15 minutes. | Write |
Each tool only returns what the client’s roles allow. Folders it can’t read don’t appear in listings, the same way they’re hidden in the web app.
Things worth knowing
Share links can’t outlive the client’s access. A link an AI client creates stops working when the client’s access expires or is revoked, or when it loses Read on the file, even if the link’s own expiry is later.
Uploads don’t overwrite by default. If a file already exists, the upload is refused. A well-behaved client asks you, then tries again with overwrite switched on. Through MCP, Write can replace files but never delete them.
Uploads have a size limit. Each upload goes in one request, so the largest file is 5 GB, or the connection’s own limit if that’s lower. Use the web app for bigger files.
Transfers happen outside the chat. Download and upload links are for the client to use with a command like curl. See how file transfers work.
Every tool call is recorded in the audit log, marked with the AI client that made it.