New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

adaptercloud_files_upload_initiate

Initiate a multipart upload session. Returns presigned URL(s) the caller must PUT bytes to, plus a sessionId to use with files_upload_complete. MCP cannot read local files; the caller is responsible for streaming bytes to the returned URL(s).

SERVERAdaptercloud SOURCE@burdenoff/adaptercloud-mcp
Medium RISK CLASS
Category Write
Parameters 73 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/burdenoff-adaptercloud-mcp/adaptercloud-files-upload-initiate.md

What adaptercloud_files_upload_initiate does on Adaptercloud

AI agents use adaptercloud_files_upload_initiate to create or update resources in Adaptercloud, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adaptercloud environment.

ParameterTypeRequiredDescription
fileName string Yes File name including extension
fileSize number Yes File size in bytes
folderId string — Target folder ID
mimeType string — MIME type (default: application/octet-stream)
extension string — File extension without leading dot
sha256Hash string Yes Hex SHA-256 of the file contents
visibility string — Visibility (default: WORKSPACE)

Parameters from the server's own tool schema.

Why adaptercloud_files_upload_initiate is rated Medium

An AI agent can call adaptercloud_files_upload_initiate faster than any human can review: one bad instruction and it creates or modifies resources in Adaptercloud by the hundred, each call as confident as the last.

Risk signalsAccepts file system path (fileName)

Questions about adaptercloud_files_upload_initiate

What does the adaptercloud_files_upload_initiate tool do? +

Initiate a multipart upload session. Returns presigned URL(s) the caller must PUT bytes to, plus a sessionId to use with files_upload_complete. MCP cannot read local files; the caller is responsible for streaming bytes to the returned URL(s). It is categorised as a Write tool in the Adaptercloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does adaptercloud_files_upload_initiate accept? +

adaptercloud_files_upload_initiate accepts 7 parameters: fileName, fileSize, folderId, mimeType, extension, sha256Hash, visibility. Required: fileName, fileSize, sha256Hash. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on adaptercloud_files_upload_initiate? +

Register the Adaptercloud MCP server in PolicyLayer and add a rule for adaptercloud_files_upload_initiate: 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 Adaptercloud. Nothing to install.

What risk level is adaptercloud_files_upload_initiate? +

adaptercloud_files_upload_initiate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit adaptercloud_files_upload_initiate? +

Yes. Add a rate_limit block to the adaptercloud_files_upload_initiate 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.

How do I block adaptercloud_files_upload_initiate completely? +

Set action: deny in the PolicyLayer policy for adaptercloud_files_upload_initiate. 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.

What MCP server provides adaptercloud_files_upload_initiate? +

adaptercloud_files_upload_initiate is provided by the Adaptercloud MCP server (@burdenoff/adaptercloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Adaptercloud, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Adaptercloud's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.