This record as markdown: /tools/linear/list-teams.md
What list_teams does on Linear
AI agents call list_teams 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 teams created on or after this ISO-8601 date-time or duration. e.g. -P1D to get teams created in the last day |
updatedAt | string | — | Return only teams updated on or after this ISO-8601 date-time or duration. e.g. -P1D to get teams updated in the last day |
includeArchived | boolean | — | Whether to include archived teams |
Parameters from the server's own tool schema.
Why list_teams is rated Low
This tool queries and returns a list of teams from the Linear workspace. It has no side effects, does not modify data, and does not execute code or trigger external operations. It is a simple read operation that retrieves organizational information accessible to the authenticated user.
From the tool's definition Tool name 'list_teams' and description 'List teams in the user's Linear workspace' indicate retrieval of team data without modification or execution of external operations.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs list_teams 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_teams, this is the rule to start with:
list_teams 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_teams call is checked against it from then on.
Questions about list_teams
List teams 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_teams accepts 8 parameters: after, limit, query, before, orderBy, createdAt, updatedAt, 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_teams: 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_teams 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_teams 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_teams. 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_teams 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