upload_to_s3
AI agents use upload_to_s3 to create or update resources in Amazon SageMaker AI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon SageMaker AI MCP Server environment.
Uploading files to S3 creates or modifies objects in a cloud storage bucket, which is a reversible Write operation. It carries high severity because uncontrolled uploads could overwrite important data, consume storage quota, or introduce malicious files into pipelines. The empty description slightly reduces confidence, but the tool name is unambiguous.
From the tool's definition Tool name 'upload_to_s3' indicates file upload to AWS S3 storage. Description is empty, but the name and context (AWS SageMaker server) clearly indicate data creation/modification in cloud storage.
Attacks that exploit this kind of access
upload_to_s3. It is categorised as a Write tool in the Amazon SageMaker AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon SageMaker AI MCP Server MCP server in PolicyLayer and add a rule for upload_to_s3: 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 Amazon SageMaker AI MCP Server. Nothing to install.
upload_to_s3 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 upload_to_s3 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 upload_to_s3. 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.
upload_to_s3 is provided by the Amazon SageMaker AI MCP Server MCP server (awslabs.sagemaker-ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.