linear_sprint_issues
AI agents call linear_sprint_issues to retrieve information from Linear MCP Integration Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name implies fetching or listing issues associated with a sprint, which is a read operation. However, the empty description reduces confidence significantly. Given the sibling tool 'linear_filter_sprint_issues' exists as a distinct read tool, this tool might have write or execute behavior, but based on naming convention the most likely interpretation is Read.
From the tool's definition Tool name 'linear_sprint_issues' suggests retrieving sprint issues; description is empty and uninformative.
Attacks that exploit this kind of access
linear_sprint_issues. It is categorised as a Read tool in the Linear MCP Integration Server MCP Server, which means it retrieves data without modifying state.
Register the Linear MCP Integration Server MCP server in PolicyLayer and add a rule for linear_sprint_issues: 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 Integration Server. Nothing to install.
linear_sprint_issues 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_sprint_issues 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_sprint_issues. 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_sprint_issues is provided by the Linear MCP Integration Server MCP server (skspade/mcp-linear-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →