linear_get_workflow_states
AI agents call linear_get_workflow_states to retrieve information from Linear MCP Integration Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Retrieving workflow states is a query operation with no side effects—it retrieves configuration or metadata about available workflow states in Linear, allowing an agent to understand valid state transitions without creating, modifying, or deleting data. This is a typical Read operation.
From the tool's definition Tool name 'linear_get_workflow_states' indicates retrieval of workflow state configuration data. Description is empty, but context from sibling tools (linear_list_projects, linear_search_issues) and the server's purpose (issue tracking and project management)…
Attacks that exploit this kind of access
linear_get_workflow_states. It is categorised as a Read tool in the Linear MCP Integration Server MCP Server, which means it retrieves data without modifying state.
Register the Linear MCP Integration Server MCP server in PolicyLayer and add a rule for linear_get_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 MCP Integration Server. Nothing to install.
linear_get_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 linear_get_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 linear_get_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.
linear_get_workflow_states is provided by the Linear MCP Integration Server MCP server (madebynando/mcp-linear-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →