remove_link
Removes a link between two artefacts after the person confirms; both artefacts stay.
Remove a link by its id, the link_id argument, as list_links lists them. Both artefacts stay; only the join goes, and with it the line in the traceability matrix. The removal goes through the same action the links panel runs and link.deleted goes out. The tool is destructive: a link is traceability, and losing one quietly would hide why a story exists, so a Heimdall turn pauses for the person's confirmation and an MCP client asks before sending. A staff token with link:delete on the project is needed.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Fires one event
Delivered to every endpoint subscribed to it once the change is made.
Annotations
A client that honours annotations asks a person before running it.
Arguments
link_id*stringUUID of the link to remove.
What it returns
{ "data": { "link_id": "e1f2a3b4-c5d6-4e7f-8a8b-9c0d1e2f3a4b", "deleted": true }}How it fails
RESOURCE_NOT_FOUNDunknown link_id, or a link outside the token's scope or the person's visibility.
FORBIDDENthe token is a client guest's, or the holder's role on the project does not carry link:delete.
TOKEN_MISSING_ABILITYtoken lacks link:delete.
How is this guide?
Last updated on