linear_list_workflow_states

List workflow states for a Linear team

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/linear-list-workflow-states.md

WHAT IT DOES

What linear_list_workflow_states does on Sage MCP

AI agents call linear_list_workflow_states to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why linear_list_workflow_states is rated Low

This tool retrieves workflow state information from a Linear team. The 'list' operation is a query that returns data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an attacker could enumerate workflow states but cannot alter team configurations or data. Classified as Read with low severity.

From the tool's definition Tool name uses 'list' verb and description states 'List workflow states' — both indicate a read-only operation that retrieves existing data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs linear_list_workflow_states safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_list_workflow_states, this is the rule to start with:

linear_list_workflow_states Allowed

linear_list_workflow_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": {
    "linear_list_workflow_states": {}
  }
}

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

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

FAQ

Questions about linear_list_workflow_states

What does the linear_list_workflow_states tool do? +

List workflow states for a Linear team. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on linear_list_workflow_states? +

Register the Sage MCP server in PolicyLayer and add a rule for linear_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 Sage MCP. Nothing to install.

What risk level is linear_list_workflow_states? +

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

Can I rate-limit linear_list_workflow_states? +

Yes. Add a rate_limit block to the linear_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.

How do I block linear_list_workflow_states completely? +

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

What MCP server provides linear_list_workflow_states? +

linear_list_workflow_states is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

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

Guides

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