Upload a file (image, video, or audio, max 50 MB) to cloud storage
AI agents use upload_file to create or update resources in SoManyLemons MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SoManyLemons MCP environment.
The upload_file tool modifies cloud storage by adding new files. While reversible (files can be deleted later), it permanently stores user-supplied content and occupies resources. This is a Write operation rather than Execute, because it does not trigger arbitrary code execution; the action is scoped to file storage.
From the tool's definition Tool description states 'Upload a file... to cloud storage' — this creates new data in persistent storage without deletion or reversal constraints.
Attacks that exploit this kind of access
Upload a file (image, video, or audio, max 50 MB) to cloud storage. It is categorised as a Write tool in the SoManyLemons MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SoManyLemons MCP server in PolicyLayer and add a rule for 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 SoManyLemons MCP. Nothing to install.
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 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_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 SoManyLemons MCP server (nomiddleinc/somanylemons-mcp). 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 →