This record as markdown: /tools/io-github-kivanccakmak-yaver/archive-extract.md
What archive_extract does on Yaver
AI agents invoke archive_extract to trigger actions in Yaver. 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 |
|---|---|---|---|
path | string | Yes | Archive file path |
destination | string | — | Extraction directory (default: current) |
Parameters from the server's own tool schema.
Why archive_extract is rated High
Extracting an archive writes files to the filesystem as a side effect of executing an extraction operation. The output depends on archive contents and target path arguments, potentially overwriting existing files. This is best classified as Execute (with Write characteristics), as it triggers a filesystem operation whose effects depend on the archive contents and destination arguments.
From the tool's definition Extract a zip or tar.gz archive
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs archive_extract safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For archive_extract, this is the rule to start with:
archive_extract 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 Yaver, apply this rule, and every archive_extract call is checked against it from then on.
Questions about archive_extract
Extract a zip or tar.gz archive. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
archive_extract accepts 2 parameters: path, destination. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for archive_extract: 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 Yaver. Nothing to install.
archive_extract 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 archive_extract 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 archive_extract. 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.
archive_extract is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue