Upload a file attachment to a page or block
AI agents use upload_file to create or update resources in Wolai MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wolai MCP Server environment.
This tool creates new data (file attachments) in a reversible manner. Users can typically delete uploaded files, making it Write rather than Destructive. The severity is medium because while file uploads are generally safe operations, they could potentially introduce malicious content, consume storage resources, or overwrite existing attachments depending on implementation details not specified in the description.
From the tool's definition Tool name is 'upload_file' and description states it uploads 'a file attachment to a page or block', which creates or adds new content to the knowledge base.
Attacks that exploit this kind of access
Upload a file attachment to a page or block. It is categorised as a Write tool in the Wolai MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wolai MCP Server 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 Wolai MCP Server. 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 Wolai MCP Server MCP server (wuchaoli/wolai-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 →