This record as markdown: /tools/cmet7-plane-mcp/add-work-item-to-cycle.md
What add_work_item_to_cycle does on Plane
AI agents use add_work_item_to_cycle 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 add_work_item_to_cycle is rated Medium
This tool modifies relationships between entities (work items and cycles) by creating an association. It is a write operation because it creates or updates data in a reversible manner—work items can be removed from cycles. While it affects project management state, the blast radius is limited to workflow organization rather than data destruction or code execution.
From the tool's definition Tool name 'add_work_item_to_cycle' and description 'Add work items to a cycle' indicate a modification operation that associates existing work items with a cycle, which is a reversible state change.
Attacks that exploit this kind of access
The rule that runs add_work_item_to_cycle safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_work_item_to_cycle, this is the rule to start with:
add_work_item_to_cycle 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Plane, apply this rule, and every add_work_item_to_cycle call is checked against it from then on.
Questions about add_work_item_to_cycle
Add work items to a cycle. 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 add_work_item_to_cycle: 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.
add_work_item_to_cycle 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 add_work_item_to_cycle 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 add_work_item_to_cycle. 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.
add_work_item_to_cycle is provided by the Plane MCP server (cmet7/plane-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Plane, and thousands of servers like it.
This server
Across the catalogue