Archive a project.
AI agents call archive_project to permanently remove resources in GitLab MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Archiving a GitLab project makes it read-only, removes it from dashboards, and disables CI/CD and contributions. While technically reversible (unarchive exists), it is a high-impact administrative action that disrupts all project activity and is categorized as destructive due to its broad, potentially irreversible-in-practice blast radius if misused by an AI agent.
From the tool's definition 'Archive a project' — archiving makes a project read-only and removes it from active use, which is a significant, difficult-to-reverse operation
Attacks that exploit this kind of access
Archive a project. It is categorised as a Destructive tool in the GitLab MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for archive_project: 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 GitLab MCP Server. Nothing to install.
archive_project 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 archive_project 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_project. 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_project is provided by the GitLab MCP Server MCP server (skmprb/gitlab-clone-mcp-server). 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 →