transfer_cycle_work_items · Plane MCP: Risk & Policy

WHAT IT DOES

What transfer_cycle_work_items does on Plane

AI agents use transfer_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 transfer_cycle_work_items needs a policy

The name suggests moving/transferring work items between cycles, which is a write/update operation (reassignment). It is likely reversible (items can be transferred back), so Write is more appropriate than Destructive. However, confidence is low due to empty description. Severity is high because bulk transfer of work items across cycles could have significant project management impact if misused.

From the tool's definition Tool name 'transfer_cycle_work_items' — no description provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transfer_cycle_work_items Rate-limited

transfer_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": {
    "transfer_cycle_work_items": {
      "limits": [
        {
          "counter": "transfer_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 transfer_cycle_work_items

What does the transfer_cycle_work_items tool do? +

transfer_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 transfer_cycle_work_items? +

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

transfer_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 transfer_cycle_work_items? +

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

Set action: deny in the PolicyLayer policy for transfer_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 transfer_cycle_work_items? +

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