AI agents call list-projects to retrieve information from Linear MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs data retrieval without modifying, executing external operations, or deleting resources. As a 'list' operation in a project management context, it has minimal blast radius—an AI agent cannot cause damage by listing projects. Confidence is slightly reduced due to the empty description, but the naming convention and sibling tools provide strong contextual evidence.
From the tool's definition Tool name 'list-projects' indicates a retrieval operation that queries and returns a list of projects. The description is empty, but the naming convention and context within a project management system strongly suggest this is a non-destructive read operation…
Documented attack patterns abuse exactly the kind of access list-projects gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linear MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list-projects:
{
"version": "1",
"default": "deny",
"tools": {
"list-projects": {}
}
}list-projects is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list-projects. It is categorised as a Read tool in the Linear MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linear MCP Server MCP server in PolicyLayer and add a rule for 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 Server. Nothing to install.
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 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 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.
list-projects is provided by the Linear MCP Server MCP server (samcfinan/linear-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Linear MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Linear MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.