This record as markdown: /tools/io-github-portel-dev-ncp/s3-upload-file.md
What s3_upload_file does on Ncp
AI agents use s3_upload_file to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why s3_upload_file is rated Medium
S3 uploads are reversible (files can be deleted), so this is Write rather than Destructive. The severity is high because unauthorized uploads could introduce malicious content, overwrite critical files, or consume storage resources, impacting availability and integrity. The confidence is high given the explicit 'upload' action and S3 bucket reference.
From the tool's definition Tool name 's3_upload_file' and description 'Upload file to S3 bucket' indicate this creates or modifies data in cloud storage. Upload operations are Write-category actions.
Attacks that exploit this kind of access
The rule that runs s3_upload_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For s3_upload_file, this is the rule to start with:
s3_upload_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 Ncp, apply this rule, and every s3_upload_file call is checked against it from then on.
Questions about s3_upload_file
Upload file to S3 bucket. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for s3_upload_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 Ncp. Nothing to install.
s3_upload_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 s3_upload_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 s3_upload_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.
s3_upload_file is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue