archive_project · Clink MCP Server MCP: Risk & Policy

WHAT IT DOES

What archive_project does on Clink MCP Server

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

WHY IT NEEDS A POLICY

Why archive_project needs a policy

The tool modifies project state by archiving it, which is a Write operation since it changes data reversibly without deletion or irreversible destruction. The severity is medium because archiving could affect team visibility and project accessibility, but the impact is reversible and localized to project metadata rather than affecting critical operations, financial data, or code execution.

From the tool's definition Tool description states: 'Archive a project. Archived projects are hidden from default views but can be reopened later.' This is a reversible modification (projects can be 'reopened later'), indicating data state change rather than deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_project Rate-limited

archive_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": {
    "archive_project": {
      "limits": [
        {
          "counter": "archive_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 Clink MCP Server, so you can run agents against it safely.

FAQ

Questions about archive_project

What does the archive_project tool do? +

Archive a project. Archived projects are hidden from default views but can be reopened later. Cannot archive the default project. It is categorised as a Write tool in the Clink 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 archive_project? +

Register the Clink 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 Clink MCP Server. Nothing to install.

What risk level is archive_project? +

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

Can I rate-limit archive_project? +

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.

How do I block archive_project completely? +

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.

What MCP server provides archive_project? +

archive_project is provided by the Clink MCP Server MCP server (voxos-ai-inc/clink-mcp-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.