linear_list_teams

List all teams in the Linear workspace.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/linear-list-teams.md

WHAT IT DOES

What linear_list_teams does on Integrations MCP

AI agents call linear_list_teams to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why linear_list_teams is rated Low

This tool retrieves team metadata from a Linear workspace without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation with minimal blast radius if misused by an AI agent—at worst, an agent learns about team structures. No destructive, financial, or execution capabilities are present.

From the tool's definition Tool name is 'linear_list_teams' with description 'List all teams in the Linear workspace.' The verb 'list' and action of retrieving/enumerating workspace teams indicates a read-only operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs linear_list_teams safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_list_teams, this is the rule to start with:

linear_list_teams Allowed

linear_list_teams is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "linear_list_teams": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every linear_list_teams call is checked against it from then on.

FAQ

Questions about linear_list_teams

What does the linear_list_teams tool do? +

List all teams in the Linear workspace. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on linear_list_teams? +

Register the Integrations MCP server in PolicyLayer and add a rule for linear_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 Integrations MCP. Nothing to install.

What risk level is linear_list_teams? +

linear_list_teams is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit linear_list_teams? +

Yes. Add a rate_limit block to the linear_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.

How do I block linear_list_teams completely? +

Set action: deny in the PolicyLayer policy for linear_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.

What MCP server provides linear_list_teams? +

linear_list_teams is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →