delete_component
Deletes a component of a project after the person confirms; the environments and repositories under it lose their component.
Delete a component by component_id. The environments and repositories that hang off it stay and lose their component; work items that touched it lose the tag. The removal goes through the same action the Components page runs and component.deleted goes out.
The tool is destructive: a Heimdall turn pauses for the person's confirmation and an MCP client asks before sending. Prefer changing a component over deleting one that work items already touch. A staff token with component: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
component_id*stringUUID of the component to delete.
What it returns
{ "data": { "component_id": "c0a1b2c3-d4e5-4f60-8a7b-9c0d1e2f3a4b", "deleted": true }}How it fails
RESOURCE_NOT_FOUNDunknown component_id, or a component 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 component:delete.
TOKEN_MISSING_ABILITYtoken lacks component:delete.
How is this guide?
Last updated on