This record as markdown: /tools/linear/linear-getworkflowstates.md
What linear_getWorkflowStates does on Linear
AI agents call linear_getWorkflowStates to retrieve information from Linear without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
teamId | string | — | ID of the team to get workflow states for |
includeArchived | boolean | — | Whether to include archived states (default: false) |
Parameters from the server's own tool schema.
Why linear_getWorkflowStates is rated Low
This tool retrieves workflow state configuration data for a team in Linear. It performs a read-only query operation with no side effects, no data modification, no code execution, and no destructive capabilities. The 'get' prefix and retrieval-based description confirm it is a Read operation. Severity is low because exposing workflow state information poses minimal risk even if accessed inappropriately.
From the tool's definition Tool name contains 'get' and description states 'Get workflow states for a team' - retrieves workflow state information without modifying data.
Attacks that exploit this kind of access
The rule that runs linear_getWorkflowStates safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linear, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_getWorkflowStates, this is the rule to start with:
linear_getWorkflowStates 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, apply this rule, and every linear_getWorkflowStates call is checked against it from then on.
Questions about linear_getWorkflowStates
Get workflow states for a team. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
linear_getWorkflowStates accepts 2 parameters: teamId, includeArchived. The full parameter table on this page comes from the server's own tool schema.
Register the Linear MCP server in PolicyLayer and add a rule for linear_getWorkflowStates: 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. Nothing to install.
linear_getWorkflowStates 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 linear_getWorkflowStates 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 linear_getWorkflowStates. 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.
linear_getWorkflowStates is provided by the Linear MCP server (@linear-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linear, and thousands of servers like it.
This server
Across the catalogue