DESTRUCTIVE

delete_stakeholder

Deletes a stakeholder of a project after the person confirms; approvals that name the seat lose an approver.

Delete a stakeholder by stakeholder_id. Approvals whose policy names the seat lose an approver; requests already open keep the approvers they were sent to. The removal goes through the same action the People page runs and stakeholder.deleted goes out. The tool is destructive: a Heimdall turn pauses for the person's confirmation and an MCP client asks before sending. A staff token with stakeholder: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.

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

Destructive

A client that honours annotations asks a person before running it.

Arguments

stakeholder_id*string

UUID of the stakeholder to delete.

What it returns

{  "data": {    "stakeholder_id": "5e6f7a8b-9c0d-4e1f-8a2b-3c4d5e6f7a8b",    "deleted": true  }}

How it fails

RESOURCE_NOT_FOUND

unknown stakeholder_id, or a stakeholder outside the token's scope or the person's visibility.

FORBIDDEN

the token is a client guest's, or the holder's role on the project does not carry stakeholder:delete.

TOKEN_MISSING_ABILITY

token lacks stakeholder:delete.

How is this guide?

Last updated on