AI agents call view-issue 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 'view-' prefix strongly suggests a read operation that retrieves issue details for display or inspection. No side effects are implied. In a project management context, viewing an issue does not create, modify, delete, or execute any external operations. Confidence is high due to clear naming convention, though empty description introduces minor uncertainty.
From the tool's definition Tool name 'view-issue' indicates retrieval of issue data. Sibling tools confirm this server performs CRUD operations; 'view-' prefix conventionally denotes read-only access without modification or deletion. Description is empty but naming convention is clear.
Documented attack patterns abuse exactly the kind of access view-issue 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 view-issue:
{
"version": "1",
"default": "deny",
"tools": {
"view-issue": {}
}
}view-issue 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.
view-issue. 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 view-issue: 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.
view-issue 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 view-issue 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 view-issue. 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.
view-issue 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.