list_project_labels
List available project labels in the Linear workspace
This record as markdown: /tools/linear/list-project-labels.md
What list_project_labels does on Linear
AI agents call list_project_labels to retrieve information from Linear without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_project_labels is rated Low
This tool retrieves and lists existing labels without modifying, creating, or deleting any data. It is a read-only operation on project metadata. The blast radius of misuse is minimal—an agent could enumerate labels but cannot affect workspace state or data integrity.
From the tool's definition Tool name 'list_project_labels' and description 'List available project labels in the Linear workspace' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_project_labels safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linear, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_project_labels, this is the rule to start with:
list_project_labels 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 Linear, apply this rule, and every list_project_labels call is checked against it from then on.
Questions about list_project_labels
List available project labels in the Linear workspace. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
Register the Linear MCP server in PolicyLayer and add a rule for list_project_labels: 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. Nothing to install.
list_project_labels 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_project_labels 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_project_labels. 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_project_labels is provided by the Linear MCP server (@linear-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linear, and thousands of servers like it.
This server
Across the catalogue