Upload a file to the sandboxed code interpreter session. Creates or overwrites a file at the specified path in the session's sandbox with the given content. Path must be relative (e.g. 'data/input.csv'). The SDK raises ValueError for absolute paths. For binary files, pass the content as a base6...
Accepts file system path (path); Accepts raw HTML/template content (content)
Part of the AWS Bedrock AgentCore MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use upload_file to create or modify resources in AWS Bedrock AgentCore MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call upload_file repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AWS Bedrock AgentCore MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
upload_file:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full AWS Bedrock AgentCore MCP Server policy for all 122 tools.
Agents calling write-class tools like upload_file have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Upload a file to the sandboxed code interpreter session. Creates or overwrites a file at the specified path in the session's sandbox with the given content. Path must be relative (e.g. 'data/input.csv'). The SDK raises ValueError for absolute paths. For binary files, pass the content as a base64-encoded string. The sandbox can then decode it, e.g. via ``import base64; data = base64.b64decode(content)``. Args: ctx: MCP context for error signaling and progress updates. session_id: The session ID to upload the file to. path: Relative file path in the sandbox (e.g. 'data/input.csv'). Must not start with '/'. content: The file content as a string. For binary files, use base64 encoding. description: Optional description of the file for LLM context. region: AWS region. Returns: FileOperationResult with path and message.. It is categorised as a Write tool in the AWS Bedrock AgentCore MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for upload_file. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Bedrock AgentCore MCP Server MCP server.
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 upload_file rule in your Intercept 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 Intercept policy for 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.
upload_file is provided by the AWS Bedrock AgentCore MCP Server MCP server (awslabs.amazon-bedrock-agentcore-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.