Archive a repository
AI agents call repo_archive to permanently remove resources in Git Steer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Archiving a repository makes it read-only and cannot be easily reversed without manual intervention; it effectively disables all write operations on the repository permanently in practice.
From the tool's definition Archive a repository
Attacks that exploit this kind of access
Archive a repository. It is categorised as a Destructive tool in the Git Steer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Git Steer MCP server in PolicyLayer and add a rule for repo_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 Git Steer. Nothing to install.
repo_archive is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the repo_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 repo_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.
repo_archive is provided by the Git Steer MCP server (ry-ops/git-steer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →