archive_extract · Yaver MCP: Risk & Policy

WHAT IT DOES

What archive_extract does on Yaver

AI agents use archive_extract to create or update resources in Yaver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

PARAMETERS

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 IT NEEDS A POLICY

Why archive_extract needs a policy

An AI agent can call archive_extract faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.

Risk signalsAccepts file system path (destination)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_extract Rate-limited

archive_extract 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "archive_extract": {
      "limits": [
        {
          "counter": "archive_extract_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about archive_extract

What does the archive_extract tool do? +

Extract a zip or tar.gz archive. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does archive_extract accept? +

archive_extract accepts 2 parameters: path, destination. Required: path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on archive_extract? +

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.

What risk level is archive_extract? +

archive_extract is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit archive_extract? +

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.

How do I block archive_extract completely? +

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.

What MCP server provides archive_extract? +

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.