manage_cycle_work_items · Plane MCP: Risk & Policy

WHAT IT DOES

What manage_cycle_work_items does on Plane

AI agents use manage_cycle_work_items 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_cycle_work_items needs a policy

The tool appears to create, update, or modify associations between work items and project cycles—reversible changes to project metadata. Without a description, confidence is moderate, but the naming pattern and server context (project management with 'create' and 'attach' operations) suggest Write-category behavior rather than read-only or destructive operations.

From the tool's definition Tool name 'manage_cycle_work_items' indicates modification of work item associations with cycles. The verb 'manage' in context of a project management server typically implies create, update, or reassign operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_cycle_work_items Rate-limited

manage_cycle_work_items 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_cycle_work_items": {
      "limits": [
        {
          "counter": "manage_cycle_work_items_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_cycle_work_items

What does the manage_cycle_work_items tool do? +

manage_cycle_work_items. 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_cycle_work_items? +

Register the Plane MCP server in PolicyLayer and add a rule for manage_cycle_work_items: 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_cycle_work_items? +

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

Can I rate-limit manage_cycle_work_items? +

Yes. Add a rate_limit block to the manage_cycle_work_items 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_cycle_work_items completely? +

Set action: deny in the PolicyLayer policy for manage_cycle_work_items. 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_cycle_work_items? +

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