manage_module_archive · Plane MCP: Risk & Policy

WHAT IT DOES

What manage_module_archive does on Plane

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

WHY IT NEEDS A POLICY

Why manage_module_archive needs a policy

Archiving/unarchiving a module modifies data state reversibly within Plane's project management system. It is not destructive (data remains intact and recoverable), not financial, and not code execution. The ability to unarchive mitigates severity to medium rather than high, as the action is not irreversible. This falls clearly into the Write category as it creates or modifies data in a reversible manner.

From the tool's definition Tool name 'manage_module_archive' and description 'Archive or unarchive a module' indicate state modification of project management entities. Archiving changes module visibility and accessibility but is reversible (unarchive capability confirms this).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_module_archive Rate-limited

manage_module_archive 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": {
    "manage_module_archive": {
      "limits": [
        {
          "counter": "manage_module_archive_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 Plane, so you can run agents against it safely.

FAQ

Questions about manage_module_archive

What does the manage_module_archive tool do? +

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

How do I enforce a policy on manage_module_archive? +

Register the Plane MCP server in PolicyLayer and add a rule for manage_module_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 Plane. Nothing to install.

What risk level is manage_module_archive? +

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

Can I rate-limit manage_module_archive? +

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

How do I block manage_module_archive completely? +

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

What MCP server provides manage_module_archive? +

manage_module_archive is provided by the Plane MCP server (@makeplane/plane-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.