linear_delete_project_update
A destructive tool on the All MCP server.
This record as markdown: /tools/allmcp/linear-delete-project-update.md
What linear_delete_project_update does on Allmcp
AI agents call linear_delete_project_update 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.
Why linear_delete_project_update is rated Critical
The tool deletes a project update, which is an irreversible action that cannot be undone. This falls squarely into the Destructive category. The severity is high because deletion of project updates could impact team workflows, documentation, and project history.
From the tool's definition Tool name is 'linear_delete_project_update' — contains the word 'delete', indicating irreversible deletion.
Attacks that exploit this kind of access
The rule that runs linear_delete_project_update 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_project_update, this is the rule to start with:
linear_delete_project_update is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Allmcp, apply this rule, and every linear_delete_project_update call is checked against it from then on.
Questions about linear_delete_project_update
linear_delete_project_update 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.
Register the All MCP server in PolicyLayer and add a rule for linear_delete_project_update: 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.
linear_delete_project_update 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 linear_delete_project_update 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_delete_project_update. 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_delete_project_update 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.
More on All, and thousands of servers like it.
Across the catalogue