extract_archive
Extract a zip archive in Nextcloud into a destination folder. Runs server-side.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/extract-archive.md
What extract_archive does on AIquila — Nextcloud MCP Server
AI agents invoke extract_archive to trigger actions in AIquila — Nextcloud MCP Server. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
archive | string | Yes | Path to the .zip file (e.g., '/Documents/backup.zip') |
overwrite | boolean | — | Whether to overwrite entries that already exist |
destination | string | Yes | Folder to extract into (e.g., '/Documents/restored') |
Parameters from the server's own tool schema.
Why extract_archive is rated High
Extracting an archive runs a server-side operation that creates/overwrites potentially many files in a destination folder. It spans Write (creates files) and could overwrite existing data, but the primary action is triggering a server-side extraction process. Since it can overwrite existing files and create arbitrary file structures, it is more severe than a simple Write.
From the tool's definition Extract a zip archive in Nextcloud into a destination folder. Runs server-side.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs extract_archive safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For extract_archive, this is the rule to start with:
extract_archive 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 AIquila — Nextcloud MCP Server, apply this rule, and every extract_archive call is checked against it from then on.
Questions about extract_archive
Extract a zip archive in Nextcloud into a destination folder. Runs server-side. It is categorised as a Execute tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
extract_archive accepts 3 parameters: archive, overwrite, destination. Required: archive, destination. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for extract_archive: 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 AIquila — Nextcloud MCP Server. Nothing to install.
extract_archive 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 extract_archive 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 extract_archive. 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.
extract_archive is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
Across the catalogue