AI agents use manage_project_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.
Archiving a project is a reversible state change operation that modifies project data but does not permanently delete it. This fits the Write category (modifies data reversibly). The severity is high because archiving a project could impact team workflows and access to work items, though it is technically reversible. The empty description reduces confidence from high to 0.75.
From the tool's definition Tool name 'manage_project_archive' implies creation, modification, or state changes to project archive status.
Attacks that exploit this kind of access
manage_project_archive. 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.
Register the Plane MCP server in PolicyLayer and add a rule for manage_project_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.
manage_project_archive is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_project_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 manage_project_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.
manage_project_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.
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 →