AI agents call list-initiatives 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 'list-' prefix is a strong signal for Read operations that retrieve data with no side effects. Absence of description lowers confidence slightly, but the tool name and its position among write/destructive operations on the same server indicate it is a simple retrieval function. Low severity because listing data poses minimal risk unless the data itself is highly sensitive (not indicated here).
From the tool's definition Tool name 'list-initiatives' follows standard listing/retrieval pattern; no description provided, but naming convention and context of sibling tools (create-*, update-*, delete-*) indicate this performs a query operation to retrieve initiatives without…
Documented attack patterns abuse exactly the kind of access list-initiatives 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 list-initiatives:
{
"version": "1",
"default": "deny",
"tools": {
"list-initiatives": {}
}
}list-initiatives 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.
list-initiatives. 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 list-initiatives: 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.
list-initiatives 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 list-initiatives 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 list-initiatives. 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.
list-initiatives 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.