DESTRUCTIVE

delete_persona

Deletes a persona of a project after the person confirms; the stories and use cases written as them keep their words.

Delete a persona by persona_id. The stories and use cases written as the persona keep their words and lose the link. The removal goes through the same action the People page runs and persona.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 persona: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

Destructive

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

Arguments

persona_id*string

UUID of the persona to delete.

What it returns

{  "data": {    "persona_id": "6f7a8b9c-0d1e-4f2a-8b3c-4d5e6f7a8b9c",    "deleted": true  }}

How it fails

RESOURCE_NOT_FOUND

unknown persona_id, or a persona 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 persona:delete.

TOKEN_MISSING_ABILITY

token lacks persona:delete.

How is this guide?

Last updated on