list_workflow_states
List all workflow states (columns) available for a team
This record as markdown: /tools/0xikarus-linear-kanban-mcp/list-workflow-states.md
What list_workflow_states does on Linear Kanban Server
AI agents call list_workflow_states to retrieve information from Linear Kanban Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_workflow_states is rated Low
This tool retrieves metadata about available workflow states in a team's Linear workspace. It is purely informational—listing existing columns/states without creating, modifying, or deleting any data. No external operations are triggered, no code is executed, and no financial obligations are incurred. This is a straightforward Read operation.
From the tool's definition Tool name is 'list_workflow_states' and description states it 'List all workflow states (columns) available for a team' - a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_workflow_states safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linear Kanban Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_workflow_states, this is the rule to start with:
list_workflow_states 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 Linear Kanban Server, apply this rule, and every list_workflow_states call is checked against it from then on.
Questions about list_workflow_states
List all workflow states (columns) available for a team. It is categorised as a Read tool in the Linear Kanban Server MCP Server, which means it retrieves data without modifying state.
Register the Linear Kanban Server MCP server in PolicyLayer and add a rule for list_workflow_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 Linear Kanban Server. Nothing to install.
list_workflow_states 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_workflow_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.
Set action: deny in the PolicyLayer policy for list_workflow_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.
list_workflow_states is provided by the Linear Kanban Server MCP server (0xikarus/linear-kanban-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linear Kanban Server, and thousands of servers like it.
This server
Across the catalogue