This record as markdown: /tools/com-files-python-mcp/upload-file-from-local.md
What Upload_File_from_Local does on Files Com
AI agents use Upload_File_from_Local to create or update resources in Files Com, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Files Com environment.
Why Upload_File_from_Local is rated Medium
This tool creates/modifies data (uploads files to Files.com) which is reversible (files can be deleted). It does not execute arbitrary code, delete data irreversibly, or move money. The 'high' severity reflects the blast radius: an AI agent could upload malicious files, overwrite legitimate files, exfiltrate data by uploading to attacker-controlled destinations, or exhaust storage quotas.
From the tool's definition Tool name 'Upload_File_from_Local' and description 'Upload a file to my Files.com site' explicitly indicate creation of new file objects in a remote cloud storage system.
Attacks that exploit this kind of access
The rule that runs Upload_File_from_Local safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Files Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For Upload_File_from_Local, this is the rule to start with:
Upload_File_from_Local 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Files Com, apply this rule, and every Upload_File_from_Local call is checked against it from then on.
Questions about Upload_File_from_Local
Upload a file to my Files.com site. It is categorised as a Write tool in the Files Com MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Files Com MCP server in PolicyLayer and add a rule for Upload_File_from_Local: 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 Files Com. Nothing to install.
Upload_File_from_Local 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_from_Local 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_from_Local. 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_from_Local is provided by the Files Com MCP server (files-com-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Files Com, and thousands of servers like it.
This server
Across the catalogue