Low Risk

linear_list_workflow_states

List workflow states for a Linear team

How to control linear_list_workflow_states ↓

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

Low Risk

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.

Documented attack patterns abuse exactly the kind of access linear_list_workflow_states gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for linear_list_workflow_states:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "linear_list_workflow_states": {}
  }
}

linear_list_workflow_states is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

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.

Enforce policy on every Sage MCP tool call.

Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.