list_states

List all workflow states in a project.

SERVERPlane SOURCEcmet7/plane-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cmet7-plane-mcp/list-states.md

WHAT IT DOES

What list_states does on Plane

AI agents call list_states 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.

RISK

Why list_states is rated Low

This tool queries and returns existing workflow state data without modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves configuration information from the project management system.

From the tool's definition Tool name 'list_states' and description 'List all workflow states in a project' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_states 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_states, this is the rule to start with:

list_states Allowed

list_states is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_states": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Plane, apply this rule, and every list_states call is checked against it from then on.

FAQ

Questions about list_states

What does the list_states tool do? +

List all workflow states in a project. It is categorised as a Read tool in the Plane MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_states? +

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

list_states is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_states? +

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

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

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

KEEP EXPLORING

More on Plane, and thousands of servers like it.

This server

All 24 Plane tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →