This record as markdown: /tools/cmet7-plane-mcp/list-cycles.md
What list_cycles does on Plane
AI agents call list_cycles to retrieve information from Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_cycles is rated Low
This tool performs a straightforward data retrieval operation (list/fetch) with no side effects, state changes, or external operations triggered. It falls squarely within the Read category. The severity is low because retrieving cycle information poses minimal risk—it neither modifies data, executes code, nor exposes sensitive operations that could be misused for harm.
From the tool's definition Tool name 'list_cycles' and description 'List all cycles in a project' indicate a read-only query operation that retrieves cycle data without modification or execution.
Attacks that exploit this kind of access
The rule that runs list_cycles 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 list_cycles, this is the rule to start with:
list_cycles is read-only, so it stays allowed. 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 list_cycles call is checked against it from then on.
Questions about list_cycles
List all cycles in a project. It is categorised as a Read tool in the Plane MCP Server, which means it retrieves data without modifying state.
Register the Plane MCP server in PolicyLayer and add a rule for list_cycles: 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.
list_cycles is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_cycles 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 list_cycles. 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.
list_cycles 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