This record as markdown: /tools/io-github-kivanccakmak-yaver/archive-create.md
What archive_create does on Yaver
AI agents use archive_create 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
format | string | — | zip or tar.gz (default: tar.gz) |
output | string | — | Output filename (auto-generated if empty) |
source | string | Yes | File or directory to archive |
Parameters from the server's own tool schema.
Why archive_create is rated Medium
This tool creates new archive files (zip or tar.gz) on the system. While reversible through deletion, it modifies the filesystem by adding new files. This is fundamentally a Write operation—creating structured data artifacts.
From the tool's definition Tool description states 'Create a zip or tar.gz archive', which is a file creation and modification operation. The verb 'Create' indicates a Write operation that produces new files.
Attacks that exploit this kind of access
The rule that runs archive_create 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_create, this is the rule to start with:
archive_create 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 Yaver, apply this rule, and every archive_create call is checked against it from then on.
Questions about archive_create
Create 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.
archive_create accepts 3 parameters: format, output, source. Required: source. 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_create: 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_create 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 archive_create 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_create. 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_create 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.
This server
Across the catalogue