AI agents use archive to create or update resources in Python — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Python environment.
The tool creates new archive files (tar, tar.gz, or zip), which is a write operation that modifies the filesystem by adding new data. While reversible through deletion, it creates new outputs and consumes resources. It does not execute arbitrary code, delete existing data irreversibly, or move money, so Write is the appropriate category.
From the tool's definition Tool description states 'Creates an archive of files from a git repository' and returns 'output file' — indicating creation of new files on the filesystem.
Attacks that exploit this kind of access
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 Python MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Python 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 Python. 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 Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
archive is one line of Python's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →