linear_update_release
A write tool on the All MCP server.
This record as markdown: /tools/allmcp/linear-update-release.md
What linear_update_release does on Allmcp
AI agents use linear_update_release to create or update resources in Allmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Allmcp environment.
Why linear_update_release is rated Medium
The 'update' action modifies existing data (a release in Linear) in a reversible manner. Without a description, confidence is reduced, but the tool name strongly suggests Write category rather than Execute (which would require arbitrary code execution capability) or Destructive (which would imply permanent deletion).
From the tool's definition Tool name is 'linear_update_release' which indicates modification of a release entity in Linear (a project management system). The 'update' verb signifies reversible data modification.
Attacks that exploit this kind of access
The rule that runs linear_update_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_update_release, this is the rule to start with:
linear_update_release 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Allmcp, apply this rule, and every linear_update_release call is checked against it from then on.
Questions about linear_update_release
linear_update_release is a write tool on the All MCP server. It is categorised as a Write tool in the Allmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the All MCP server in PolicyLayer and add a rule for linear_update_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.
linear_update_release 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_update_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.
Set action: deny in the PolicyLayer policy for linear_update_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.
linear_update_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.
More on All, and thousands of servers like it.
This server
Across the catalogue