This record as markdown: /tools/com-files-python-mcp/unzip-file.md
What Unzip_File does on Files Com
AI agents invoke Unzip_File to trigger actions in Files Com. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why Unzip_File is rated High
Unzipping a file triggers an external operation that creates multiple files/folders at the destination, potentially overwriting existing content. This is more than a simple write—it executes an extraction process whose effects depend on the ZIP archive contents (could overwrite files, create arbitrary directory structures, or expand to large amounts of data), making Execute the appropriate category.
From the tool's definition Extract a ZIP file to a destination folder
Attacks that exploit this kind of access
The rule that runs Unzip_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 Unzip_File, this is the rule to start with:
Unzip_File stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 Unzip_File call is checked against it from then on.
Questions about Unzip_File
Extract a ZIP file to a destination folder. It is categorised as a Execute tool in the Files Com MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Files Com MCP server in PolicyLayer and add a rule for Unzip_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.
Unzip_File is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the Unzip_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 Unzip_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.
Unzip_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.
Across the catalogue