linear_get_issue_history

A read tool on the All MCP server.

SERVERAllmcp SOURCEPerception-Dynamics-Inc/allmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/allmcp/linear-get-issue-history.md

WHAT IT DOES

What linear_get_issue_history does on Allmcp

AI agents call linear_get_issue_history 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.

RISK

Why linear_get_issue_history is rated Low

The 'get' verb and 'history' suffix strongly suggest this tool retrieves historical information about issues without modifying state. Although the description is empty (reducing confidence slightly), the naming convention and context among sibling tools (which include explicit create/delete operations) indicate this is a read operation with no side effects.

From the tool's definition Tool name 'linear_get_issue_history' contains 'get' and 'history', indicating data retrieval. No description provided, but the naming pattern is consistent with read-only query operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs linear_get_issue_history 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_get_issue_history, this is the rule to start with:

linear_get_issue_history Allowed

linear_get_issue_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "linear_get_issue_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Allmcp, apply this rule, and every linear_get_issue_history call is checked against it from then on.

FAQ

Questions about linear_get_issue_history

What does the linear_get_issue_history tool do? +

linear_get_issue_history 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.

How do I enforce a policy on linear_get_issue_history? +

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

What risk level is linear_get_issue_history? +

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

Can I rate-limit linear_get_issue_history? +

Yes. Add a rate_limit block to the linear_get_issue_history 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_get_issue_history completely? +

Set action: deny in the PolicyLayer policy for linear_get_issue_history. 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_get_issue_history? +

linear_get_issue_history 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.

KEEP EXPLORING

More on All, and thousands of servers like it.

This server

All 501 All tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →