AI agents use linear_createIssueFromTemplate to create or update resources in Linear — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear environment.
This tool creates a new issue, which is a reversible data modification operation. It does not delete, execute arbitrary code, or move money. Creation of project management issues is a typical Write operation. Severity is medium because misuse could create spam or noise in the project management system, but the blast radius is limited to data creation and does not affect financial systems or cause irreversible damage.
From the tool's definition Tool name 'linear_createIssueFromTemplate' and description 'Create a new issue from a template' both indicate creation of new data (an issue).
Documented attack patterns abuse exactly the kind of access linear_createIssueFromTemplate 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_createIssueFromTemplate:
{
"version": "1",
"default": "deny",
"tools": {
"linear_createIssueFromTemplate": {
"limits": [
{
"counter": "linear_createissuefromtemplate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}linear_createIssueFromTemplate stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new issue from a template. It is categorised as a Write tool in the Linear MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linear MCP server in PolicyLayer and add a rule for linear_createIssueFromTemplate: 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.
linear_createIssueFromTemplate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the linear_createIssueFromTemplate 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_createIssueFromTemplate. 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_createIssueFromTemplate 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.
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.