get_issue_status
Retrieve detailed information about an issue status in Linear by name or ID
This record as markdown: /tools/linear/get-issue-status.md
What get_issue_status does on Linear
AI agents call get_issue_status 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 |
|---|---|---|---|
id | string | — | The ID of the issue status to retrieve |
name | string | — | The name of the issue status to retrieve |
team | string | — | The team name or ID |
Parameters from the server's own tool schema.
Why get_issue_status is rated Low
This tool retrieves metadata about an issue status without creating, modifying, or deleting any data. It is a simple read operation consistent with get/fetch patterns. The blast radius is minimal—at worst, an agent might retrieve incorrect information but cannot cause harm.
From the tool's definition Tool name 'get_issue_status' and description 'Retrieve detailed information about an issue status in Linear by name or ID' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_issue_status 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 get_issue_status, this is the rule to start with:
get_issue_status 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 get_issue_status call is checked against it from then on.
Questions about get_issue_status
Retrieve detailed information about an issue status in Linear by name or ID. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
get_issue_status accepts 3 parameters: id, name, team. 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 get_issue_status: 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.
get_issue_status 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 get_issue_status 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 get_issue_status. 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.
get_issue_status 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