Niches · File storage & sharing

Give an agent access to one bucket or folder and nothing else

Four or more companies' docs show a full fit.

6companies, full fit
6companies, fit with a limit
9companies carry the tag
19share of the category's work
7first-hand accounts

What counts as done

A credential limited to one bucket, prefix or folder with chosen verbs (read, write without delete), created, rotated and revoked through the API, and deletes recoverable for a set period.

How agents ask for it: let the agent write to the uploads bucket only, give it read-only access to the cache, make sure it can't delete anything, rotate the leaked key

Does the job 6

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Amazon S3 A
Amazon Web Services, Inc.
Bucket and IAM policies scope by prefix and action, so PutObject can be allowed without DeleteObject. IAM CreateAccessKey manages keys by API, and versioning keeps deleted objects with noncurrent-expiry rules. source
Azure Blob Storage BB
Microsoft Corporation
RBAC on one container with ABAC conditions on blob path, blobs/write separate from blobs/delete, key regeneration through the management REST API, and soft delete retention of 1 to 365 days. source
Backblaze B2 A
Backblaze, Inc.
Standard application keys limit to one bucket and a name prefix with chosen capabilities (writeFiles without deleteFiles) and an expiry, made by b2_create_key; deleted files stay as hidden versions until a lifecycle rule removes them. source
Box API + MCP B
Box, Inc.
POST /oauth2/token downscopes a token to chosen scopes and one item's URL, so upload can be granted without delete. Tokens can be revoked by API, and trashed items stay restorable until the purge window. source
Google Cloud Storage A
Google LLC (Google Cloud EMEA Limited and other regional entities by billing address)
IAM on a bucket or managed folder, HMAC keys created and deleted through the API for a service account, and soft delete keeps deleted objects for 7 to 90 days. source
Wasabi Hot Cloud Storage B
Wasabi Technologies LLC
Sub-users take IAM policies limited to one bucket and chosen S3 actions, STS AssumeRole issues temporary credentials with inline policies, each user holds two rotatable keys, and versioning or Object Lock makes deletes recoverable. source

Does the job, with a limit 7

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Cloudflare R2 A
Cloudflare, Inc.
Tokens scope to buckets, and temporary credentials narrow to prefixes and a list of S3 actions, so write without delete is possible. With no versioning, deleted objects can't be recovered; bucket locks only block deletion. source
DigitalOcean Spaces B
DigitalOcean, LLC
Limited keys grant Read or Read/Write/Delete per bucket, with no prefix and no write-without-delete (a named blocker). POST /v2/spaces/keys manages keys by API, but acc-29 couldn't rotate one from an agent session without a DigitalOcean token. source
Dropbox API + MCP B
Dropbox, Inc.
App Folder access roots an app in one folder, and deleted files can be restored. The pages read show no scope for write without delete, and key rotation is OAuth token revocation rather than storage keys. source
Fastio C
VividEngine, LLC (doing business as Fast Technologies)
API keys and service-account keys can be scoped to one workspace with r or rw and an expiry, created by API, and a trash folder exists. There is no write-without-delete grant. source
Google Drive API + MCP BB
Google LLC
drive.file limits an app to files it made or the user picked, which can't reach existing files (acc-19); sharing one folder to a service account is the folder-level option. No write-without-trash role; trash is recoverable. source
OneDrive and SharePoint files (Microsoft Graph) B
Microsoft Corporation
Sites.Selected and Files.SelectedOperations.Selected let an admin grant an app access to one site, library, folder or file with read or write roles. No write-without-delete role was found, and recycle-bin retention wasn't read. source
Tigris C
Tigris Data Inc.
Access keys take per-bucket roles, but Editor is read, write and delete and ReadOnly reads only, so write-without-delete needs an IAM policy, which I didn't read. Keys are deleted to revoke, and snapshot-enabled buckets recover deleted files. source

Doesn't do this job 2

Listings in the category that do something else, with the reason.

ListingWhy
Bunny Storage B
BunnyWay d.o.o.
The only storage credential is a zone password, read-write or read-only, with no prefix scope or write-without-delete; acc-21 found the account API key doesn't reach storage. source
ONLYOFFICE Apps MCP Server D
Ascensio System SIA
The hosted server's OAuth proxy hands every client one shared OAuth application and changes scope handling, and toolsets limit tools rather than the credential; no folder-scoped key is offered. source

What stops agents finishing

  • keys are per account, or rotation needs a console sign-in
  • no write-without-delete verb
  • the drive's narrow scope breaks the tools the agent needs

Around it

Before: secrets.store. After: file-storage.agent-upload.

Where this comes from

Weight 19 of 100 in File storage & sharing: 7 of 36 links; issues where operators narrow an agent's reach or found they could not

The same as data: /api/v1/use-cases/file-storage.scoped-access.json, or the MCP tool get_use_case with id file-storage.scoped-access. Other jobs in this category: /api/v1/niches?category=file-storage.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.