This record as markdown: /tools/linear/list-documents.md
What list_documents does on Linear
AI agents call list_documents 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 |
|---|---|---|---|
after | string | — | An ID to start from |
limit | number | — | The number of results to return (Max is 250) |
query | string | — | An optional search query |
before | string | — | An ID to end at |
orderBy | string | — | The order in which to return results |
createdAt | string | — | Return only documents created on or after this ISO-8601 date-time or duration. e.g. -P1D to get documents created in the last day |
creatorId | string | — | Filter by creator ID |
projectId | string | — | Filter by project ID |
updatedAt | string | — | Return only documents updated on or after this ISO-8601 date-time or duration. e.g. -P1D to get documents updated in the last day |
initiativeId | string | — | Filter by initiative ID |
includeArchived | boolean | — | Whether to include archived documents |
Parameters from the server's own tool schema.
Why list_documents is rated Low
The tool retrieves and lists existing documents without creating, modifying, deleting, or executing operations. It is a straightforward read operation with minimal blast radius if misused by an agent—worst case would be enumeration of workspace documents, which causes no data loss or system changes.
From the tool's definition Tool name is "list_documents" and description states it "List documents in the user's Linear workspace". This is a query/retrieval operation with no modification capability.
Risk signalsAccepts freeform code/query input (query) · High parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs list_documents 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 list_documents, this is the rule to start with:
list_documents 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 list_documents call is checked against it from then on.
Questions about list_documents
List documents in the user's Linear workspace. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
list_documents accepts 11 parameters: after, limit, query, before, orderBy, createdAt, creatorId, projectId, updatedAt, initiativeId, includeArchived. 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 list_documents: 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.
list_documents 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 list_documents 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 list_documents. 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.
list_documents 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