unlink-project-from-initiative
AI agents call unlink-project-from-initiative to permanently remove resources in Linear MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Unlinking a project from an initiative removes an association that may not be easily recoverable, which is more destructive than a simple write. The sibling tool 'link-project-to-initiative' is the inverse operation, suggesting this removes that link. Confidence is moderate because the description is empty and we're inferring behavior from the name and context of sibling tools.
From the tool's definition Tool name: 'unlink-project-from-initiative' — the 'unlink' action implies removing an existing relationship/association between a project and an initiative.
Documented attack patterns abuse exactly the kind of access unlink-project-from-initiative 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 unlink-project-from-initiative:
{
"version": "1",
"default": "deny",
"hide": [
"unlink-project-from-initiative"
]
} unlink-project-from-initiative disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
unlink-project-from-initiative. It is categorised as a Destructive tool in the Linear MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Linear MCP Server MCP server in PolicyLayer and add a rule for unlink-project-from-initiative: 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.
unlink-project-from-initiative is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the unlink-project-from-initiative 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 unlink-project-from-initiative. 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.
unlink-project-from-initiative 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.