This record as markdown: /tools/7gugu-zip-mcp/decompress.md
What decompress does on ZIP-MCP
AI agents use decompress to create or update resources in ZIP-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ZIP-MCP environment.
Why decompress is rated Medium
Decompressing a ZIP file writes new files and directories to the filesystem. This is reversible (the extracted files can be deleted), so it falls under Write rather than Destructive. However, it could overwrite existing files at the destination path, which raises the severity to medium. It does not execute code or move money.
From the tool's definition 'Decompress local ZIP file to specified directory' — creates new files in a target directory
Attacks that exploit this kind of access
The rule that runs decompress safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ZIP-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For decompress, this is the rule to start with:
decompress 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 ZIP-MCP, apply this rule, and every decompress call is checked against it from then on.
Questions about decompress
Decompress local ZIP file to specified directory. It is categorised as a Write tool in the ZIP-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ZIP MCP server in PolicyLayer and add a rule for decompress: 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 ZIP-MCP. Nothing to install.
decompress 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 decompress 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 decompress. 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.
decompress is provided by the ZIP MCP server (7gugu/zip-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ZIP, and thousands of servers like it.
This server
Across the catalogue