Upload a file into a VM. Pass content as base64 string (max 50MB).
AI agents use file_upload to create or update resources in Taw Computer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Taw Computer environment.
file_upload creates new files or overwrites existing files on the VM filesystem. This is a write operation (Write > Read) because it modifies state. Severity is high rather than medium due to the 50MB size limit enabling potential storage exhaustion, malicious executable uploads, or writing to sensitive system paths.
From the tool's definition Tool name 'file_upload' and description 'Upload a file into a VM' explicitly perform write operations to storage within the VM environment.
Documented attack patterns abuse exactly the kind of access file_upload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Taw Computer, and nothing reaches the server without passing your rules. This is the rule we recommend for file_upload:
{
"version": "1",
"default": "deny",
"tools": {
"file_upload": {
"limits": [
{
"counter": "file_upload_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}file_upload 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.
Free to start. No card required.
Upload a file into a VM. Pass content as base64 string (max 50MB). It is categorised as a Write tool in the Taw Computer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Taw Computer MCP server in PolicyLayer and add a rule for file_upload: 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 Taw Computer. Nothing to install.
file_upload 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 file_upload 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 file_upload. 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.
file_upload is provided by the Taw Computer MCP server (tawgroup/taw-computer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Taw Computer, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 Taw Computer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.