delete_repository
Removes a repository from a project's registry after the person confirms; the code itself is untouched.
Remove a repository by repository_id. The registry row goes; the code on the provider is untouched, and the integration stops linking to it. The removal goes through the same action the Repositories page runs and repository.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 repository: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
repository_id*stringUUID of the repository to remove.
What it returns
{ "data": { "repository_id": "4c5d6e7f-8a9b-4c0d-8e1f-2a3b4c5d6e7f", "deleted": true }}How it fails
RESOURCE_NOT_FOUNDunknown repository_id, or a repository 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 repository:delete.
TOKEN_MISSING_ABILITYtoken lacks repository:delete.
How is this guide?
Last updated on