linear_search_teams
AI agents call linear_search_teams to retrieve information from Linear MCP Integration Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries teams data from Linear without modifying state. The 'search' verb confirms it is a Read operation. Confidence is slightly reduced (0.85 vs higher) due to the empty description, but the strong contextual evidence from sibling tools and the clear verb choice supports Read classification with low severity.
From the tool's definition Tool name 'linear_search_teams' with 'search' verb indicates data retrieval. Sibling tools like 'linear_search_issues', 'linear_list_projects', and 'linear_get_workflow_states' are all Read operations.
Attacks that exploit this kind of access
linear_search_teams. It is categorised as a Read tool in the Linear MCP Integration Server MCP Server, which means it retrieves data without modifying state.
Register the Linear MCP Integration Server MCP server in PolicyLayer and add a rule for linear_search_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 MCP Integration Server. Nothing to install.
linear_search_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 linear_search_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 linear_search_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.
linear_search_teams is provided by the Linear MCP Integration Server MCP server (madebynando/mcp-linear-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →