linear_delete_release

A destructive tool on the All MCP server.

SERVERAllmcp SOURCEPerception-Dynamics-Inc/allmcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/allmcp/linear-delete-release.md

WHAT IT DOES

What linear_delete_release does on Allmcp

AI agents call linear_delete_release to permanently remove resources in Allmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why linear_delete_release is rated Critical

The 'delete' operation combined with 'release' targets (which are normally permanent and traceable) indicates a destructive action. While the description is empty, the naming convention is unambiguous.

From the tool's definition Tool name explicitly contains 'delete' and 'release'. The function operates on releases, which are typically immutable deployment artifacts or versioned milestones that cannot be trivially recreated. Deletion of releases is an irreversible action.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs linear_delete_release safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_delete_release, this is the rule to start with:

linear_delete_release Hidden

linear_delete_release is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "linear_delete_release"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Allmcp, apply this rule, and every linear_delete_release call is checked against it from then on.

FAQ

Questions about linear_delete_release

What does the linear_delete_release tool do? +

linear_delete_release is a destructive tool on the All MCP server. It is categorised as a Destructive tool in the Allmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on linear_delete_release? +

Register the All MCP server in PolicyLayer and add a rule for linear_delete_release: 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 Allmcp. Nothing to install.

What risk level is linear_delete_release? +

linear_delete_release is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit linear_delete_release? +

Yes. Add a rate_limit block to the linear_delete_release 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.

How do I block linear_delete_release completely? +

Set action: deny in the PolicyLayer policy for linear_delete_release. 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.

What MCP server provides linear_delete_release? +

linear_delete_release is provided by the All MCP server (Perception-Dynamics-Inc/allmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on All, and thousands of servers like it.

This server

All 501 All tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →