AI agents use upload_file to create or update resources in Pydoll — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pydoll environment.
This tool performs a Write operation because it uploads files to web forms, creating or adding data to a destination. While upload operations can have side effects depending on what the receiving form does with the file, the tool itself is fundamentally a write/create action.
From the tool's definition upload_file: Upload a file to a web form. The tool description explicitly indicates it creates or modifies data by uploading files to web forms, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access upload_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pydoll, and nothing reaches the server without passing your rules. This is the rule we recommend for upload_file:
{
"version": "1",
"default": "deny",
"tools": {
"upload_file": {
"limits": [
{
"counter": "upload_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upload_file 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 to a web form. It is categorised as a Write tool in the Pydoll MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pydoll 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 Pydoll. 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 Pydoll MCP server (jinsongroh/pydoll-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pydoll, 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.
57 Pydoll tools catalogued and risk-classified — across an index of 43,000+ MCP servers.