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-http/archive.md
What archive does on Http
AI agents use archive to create or update resources in Http, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Http environment.
Why archive is rated Medium
This tool creates new files/archives without deleting or irreversibly modifying existing data. It is Write rather than Execute because the primary function is file creation, not arbitrary command execution. Severity is medium because malicious archive creation could consume disk space or create files with misleading content, but the effects are reversible (archives can be deleted).
From the tool's definition Tool description states 'Creates an archive of files from a git repository.' The verb 'creates' indicates data modification. It produces output files (tar, tar.gz, zip) that represent new artifacts derived from repository content.
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 Http, 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 Http, 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 Http MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Http 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 Http. 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 Http MCP server (@paretools/http). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Http, and thousands of servers like it.
This server
Across the catalogue