This record as markdown: /tools/linear/get-document.md
What get_document does on Linear
AI agents call get_document 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 document ID or slug |
Parameters from the server's own tool schema.
Why get_document is rated Low
The verb 'retrieve' and the absence of any mutation, side effects, or parameter that could modify state indicate this is a Read operation. The tool queries and returns document data. Severity is low because document retrieval has minimal blast radius—it only accesses existing information that the user may already have authorization to view.
From the tool's definition Tool name 'get_document' with description 'Retrieve a Linear document by ID or slug' indicates a read-only operation that fetches data without modification.
Attacks that exploit this kind of access
The rule that runs get_document 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_document, this is the rule to start with:
get_document 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_document call is checked against it from then on.
Questions about get_document
Retrieve a Linear document by ID or slug. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
get_document accepts 1 parameter: id. 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_document: 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_document 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_document 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_document. 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_document 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