linear_getInitiativeById
Get details of a specific initiative by ID
This record as markdown: /tools/linear/linear-getinitiativebyid.md
What linear_getInitiativeById does on Linear
AI agents call linear_getInitiativeById 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 |
|---|---|---|---|
initiativeId | string | — | The ID of the initiative to retrieve |
includeProjects | boolean | — | Include associated projects in the response |
Parameters from the server's own tool schema.
Why linear_getInitiativeById is rated Low
This tool queries and retrieves information about an initiative without altering any data. It is a read-only operation consistent with the Read category pattern (get/fetch/retrieve operations). Severity is low because unauthorized access to initiative details poses minimal direct risk; the blast radius is limited to information disclosure.
From the tool's definition Tool name contains 'get' and description states 'Get details of a specific initiative by ID' — a straightforward retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs linear_getInitiativeById 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_getInitiativeById, this is the rule to start with:
linear_getInitiativeById 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_getInitiativeById call is checked against it from then on.
Questions about linear_getInitiativeById
Get details of a specific initiative by ID. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
linear_getInitiativeById accepts 2 parameters: initiativeId, includeProjects. 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_getInitiativeById: 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_getInitiativeById 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_getInitiativeById 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_getInitiativeById. 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_getInitiativeById 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