unarchive_project · GitLab MCP Server MCP: Risk & Policy

WHAT IT DOES

What unarchive_project does on GitLab MCP Server

AI agents use unarchive_project to create or update resources in GitLab MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitLab MCP Server environment.

WHY IT NEEDS A POLICY

Why unarchive_project needs a policy

This tool modifies project state by reversing an archive operation, making it a Write-category action rather than Read or Execute. It's reversible (can be re-archived), and the blast radius is moderate—unarchiving a project restores visibility and access to a project that was previously hidden, potentially affecting team workflows and access controls, but this is not irreversible or financial in nature.

From the tool's definition Tool name 'unarchive_project' and description 'Unarchive a project.' indicate a state change operation that reverses a previous archive action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unarchive_project Rate-limited

unarchive_project 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "unarchive_project": {
      "limits": [
        {
          "counter": "unarchive_project_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitLab MCP Server, so you can run agents against it safely.

FAQ

Questions about unarchive_project

What does the unarchive_project tool do? +

Unarchive a project. It is categorised as a Write tool in the GitLab MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on unarchive_project? +

Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for unarchive_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.

What risk level is unarchive_project? +

unarchive_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit unarchive_project? +

Yes. Add a rate_limit block to the unarchive_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.

How do I block unarchive_project completely? +

Set action: deny in the PolicyLayer policy for unarchive_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.

What MCP server provides unarchive_project? +

unarchive_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.