archive
Creates an archive of files from a git repository. Supports tar, tar.gz, and zip formats. Returns structured data with success status, format, output file, and treeish.
This record as markdown: /tools/io-github-dave-london-pare-search/archive.md
What archive does on Search
AI agents use archive to create or update resources in Search, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Search environment.
Why archive is rated Medium
The tool creates new archive files as output, which is a write operation that modifies filesystem state. However, it does not delete or irreversibly overwrite existing data, and the operation is reversible (archives can be deleted). It does not execute arbitrary code, move money, or perform a Read-only operation.
From the tool's definition 'Creates an archive of files from a git repository' — this operation writes/creates new files (archive outputs) on the filesystem. It modifies the system state by producing new artifacts.
Attacks that exploit this kind of access
The rule that runs archive safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Search, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For archive, this is the rule to start with:
archive 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 Search, apply this rule, and every archive call is checked against it from then on.
Questions about archive
Creates an archive of files from a git repository. Supports tar, tar.gz, and zip formats. Returns structured data with success status, format, output file, and treeish. It is categorised as a Write tool in the Search MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Search MCP server in PolicyLayer and add a rule for 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 Search. Nothing to install.
archive 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 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. 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 is provided by the Search MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Search, and thousands of servers like it.
This server
Across the catalogue