AI agents call linear_get_team to retrieve information from Linearapp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves team information without modifying, creating, deleting, executing code, or affecting financial data. It is a straightforward read operation that queries existing data from the Linear API.
From the tool's definition Tool name is 'linear_get_team' and description states 'Get details about a specific team' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get details about a specific team. It is categorised as a Read tool in the Linearapp MCP Server, which means it retrieves data without modifying state.
Register the Linearapp MCP server in PolicyLayer and add a rule for linear_get_team: 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 Linearapp. Nothing to install.
linear_get_team 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_get_team 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_get_team. 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_get_team is provided by the Linearapp MCP server (mcp-server-linearapp). 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 →