Upload a folder to Proton Drive (copies all contents recursively)
AI agents use drive__upload_folder to create or update resources in Proton-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Proton-MCP environment.
This tool creates new data in Proton Drive by uploading entire folder structures. While not destructive (data is not deleted or irreversibly overwritten), it is a Write operation that modifies the user's cloud storage state.
From the tool's definition Tool name 'drive__upload_folder' and description 'Upload a folder to Proton Drive (copies all contents recursively)' indicate creation/addition of data to cloud storage.
Documented attack patterns abuse exactly the kind of access drive__upload_folder gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proton-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for drive__upload_folder:
{
"version": "1",
"default": "deny",
"tools": {
"drive__upload_folder": {
"limits": [
{
"counter": "drive__upload_folder_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} drive__upload_folder 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 folder to Proton Drive (copies all contents recursively). It is categorised as a Write tool in the Proton-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Proton- MCP server in PolicyLayer and add a rule for drive__upload_folder: 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 Proton-MCP. Nothing to install.
drive__upload_folder 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 drive__upload_folder 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 drive__upload_folder. 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.
drive__upload_folder is provided by the Proton- MCP server (jorgenclaw/proton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Proton-MCP, 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 Proton-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.