linear_list_project_statuses
A read tool on the All MCP server.
This record as markdown: /tools/allmcp/linear-list-project-statuses.md
What linear_list_project_statuses does on Allmcp
AI agents call linear_list_project_statuses to retrieve information from Allmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why linear_list_project_statuses is rated Low
The 'list' verb in the tool name denotes a read-only query operation that retrieves project statuses from a Linear integration. This has no side effects on data — it only fetches information. Although the description is empty (lowering confidence slightly), the tool name structure is clear and consistent with standard read operation naming.
From the tool's definition Tool name 'linear_list_project_statuses' indicates a list/retrieval operation on project status data without mutation capability. No description provided to contradict this inference.
Attacks that exploit this kind of access
The rule that runs linear_list_project_statuses safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Allmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_list_project_statuses, this is the rule to start with:
linear_list_project_statuses is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Allmcp, apply this rule, and every linear_list_project_statuses call is checked against it from then on.
Questions about linear_list_project_statuses
linear_list_project_statuses is a read tool on the All MCP server. It is categorised as a Read tool in the Allmcp MCP Server, which means it retrieves data without modifying state.
Register the All MCP server in PolicyLayer and add a rule for linear_list_project_statuses: 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 Allmcp. Nothing to install.
linear_list_project_statuses 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_project_statuses 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_project_statuses. 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_project_statuses is provided by the All MCP server (Perception-Dynamics-Inc/allmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on All, and thousands of servers like it.
This server
Across the catalogue