Zip_File
Create a ZIP from one or more paths and save it to a destination path.
This record as markdown: /tools/com-files-python-mcp/zip-file.md
What Zip_File does on Files Com
AI agents use Zip_File 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 Zip_File is rated Medium
The tool creates a new file artifact by compressing data, which is a reversible write operation. While it doesn't directly modify or delete existing data, it does create a new file in the destination path. If an AI agent misuses this tool, it could consume disk space or create unintended archives, but the operation itself is reversible (the ZIP can be deleted).
From the tool's definition Tool creates a new ZIP file ("Create a ZIP from one or more paths and save it to a destination path"), which is a data creation and storage operation.
Attacks that exploit this kind of access
The rule that runs Zip_File 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 Zip_File, this is the rule to start with:
Zip_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Files Com, apply this rule, and every Zip_File call is checked against it from then on.
Questions about Zip_File
Create a ZIP from one or more paths and save it to a destination path. 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 Zip_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 Files Com. Nothing to install.
Zip_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 Zip_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 Zip_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.
Zip_File 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