DESTRUCTIVE

delete_change_request

Deletes a change request that was never agreed, with its links and versions; a request past its gate is closed rather than deleted, and its number is never handed out again.

Remove a change request that is still submitted, under_analysis or rejected. The request, its links to the records it touched and every version of it are deleted; the records themselves are untouched, and the number stays spent. A request that is awaiting approval, approved or anywhere in the work after it cannot be deleted: withdraw the approval first, or close the request instead. Marked destructive, so a client confirms before running it. Runs the same action as Delete Change Request in the application and emits change_request.deleted.

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

change_request_id*string

UUID of the change request to delete.

What it returns

{  "data": {    "change_request_id": "c7d8e9f0-a1b2-4c3d-8e4f-5a6b7c8d9e0f",    "deleted": true  }}

How it fails

VALIDATION_FAILED

the request is awaiting approval, approved, implementing, implemented, verified or closed; nothing is deleted.

RESOURCE_NOT_FOUND

unknown change_request_id, or a request outside the token's scope.

FORBIDDEN

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

TOKEN_MISSING_ABILITY

token lacks change-request:delete.

How is this guide?

Last updated on