Upload object to S3
AI agents use aws_s3_upload_object to create or update resources in AWS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS MCP Server environment.
Uploading to S3 creates or modifies objects in cloud storage, which is a reversible write operation. However, it carries high severity because uncontrolled uploads could exhaust storage quotas, introduce malicious content, or overwrite critical data in shared buckets.
From the tool's definition Tool name 'aws_s3_upload_object' and description 'Upload object to S3' indicate creation/modification of data in S3 buckets. S3 is a persistent storage service where uploaded objects become part of the system state.
Attacks that exploit this kind of access
Upload object to S3. It is categorised as a Write tool in the AWS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS MCP Server MCP server in PolicyLayer and add a rule for aws_s3_upload_object: 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 AWS MCP Server. Nothing to install.
aws_s3_upload_object 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 aws_s3_upload_object 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 aws_s3_upload_object. 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.
aws_s3_upload_object is provided by the AWS MCP Server MCP server (lokimcpuniverse/aws-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →