linear_list_projects
AI agents call linear_list_projects 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.
The tool name strongly indicates a read-only operation that retrieves a list of projects from Linear. No description is provided, which slightly lowers confidence, but the naming convention and context among read-oriented sibling tools (search, filter, get operations) supports classification as Read with low severity—listing projects has minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'linear_list_projects' indicates a listing/retrieval operation. The verb 'list' is a Read operation pattern.
Attacks that exploit this kind of access
linear_list_projects. 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_list_projects: 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_list_projects 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_list_projects 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_list_projects. 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_list_projects 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 →