delete_environment
Deletes an environment of a project after the person confirms.
Delete an environment by environment_id. The removal goes through the same action the Environments page runs and environment.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 environment: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
environment_id*stringUUID of the environment to delete.
What it returns
{ "data": { "environment_id": "e1f2a3b4-c5d6-4e7f-8a9b-0c1d2e3f4a5b", "deleted": true }}How it fails
RESOURCE_NOT_FOUNDunknown environment_id, or an environment 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 environment:delete.
TOKEN_MISSING_ABILITYtoken lacks environment:delete.
How is this guide?
Last updated on