Low Risk

linear_getCustomerNeeds

Get customer needs from Linear

How to control linear_getCustomerNeeds ↓

AI agents call linear_getCustomerNeeds to retrieve information from Linear without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves or queries customer needs data from the Linear system without modifying, creating, or deleting any data. It is a pure read operation that returns information to the user. No irreversible actions, code execution, or financial transactions are involved. The low severity reflects minimal risk from misuse—an agent retrieving customer needs data poses no significant blast radius.

From the tool's definition Tool name 'getCustomerNeeds' and description 'Get customer needs from Linear' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access linear_getCustomerNeeds gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Linear, and nothing reaches the server without passing your rules. This is the rule we recommend for linear_getCustomerNeeds:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "linear_getCustomerNeeds": {}
  }
}

linear_getCustomerNeeds is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Linear — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the linear_getCustomerNeeds tool do? +

Get customer needs from Linear. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on linear_getCustomerNeeds? +

Register the Linear MCP server in PolicyLayer and add a rule for linear_getCustomerNeeds: 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.

What risk level is linear_getCustomerNeeds? +

linear_getCustomerNeeds is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit linear_getCustomerNeeds? +

Yes. Add a rate_limit block to the linear_getCustomerNeeds 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.

How do I block linear_getCustomerNeeds completely? +

Set action: deny in the PolicyLayer policy for linear_getCustomerNeeds. 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.

What MCP server provides linear_getCustomerNeeds? +

linear_getCustomerNeeds is provided by the Linear MCP server (tacticlaunch/mcp-linear). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Linear tool call.

Deterministic rules across all 182 Linear tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

182 Linear tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.