update_raid_item
Changes a RAID item in part and moves it along its lifecycle when a status is sent.
Change a RAID item by raid_item_id with any of title, type, description (HTML), category, probability, impact, mitigation, contingency, owner_id, due_on, review_on, depends_on and status (open, monitoring, mitigating, resolved, closed, occurred or accepted; a closed item goes back to open only). A field left out keeps its value; a field sent as null is cleared. The fields go through the same action the RAID Log page runs and write a version; raid_item.updated goes out. A status goes through its own move and raid_item.status_changed goes out. A staff token with raid:update 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 actions as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Fires events
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
raid_item_id*stringUUID of the RAID item.
titlestringoptionalWhat the item is called, 3 to 200 characters.
typestringoptionalRisk, assumption, issue or dependency; risk by default.
riskassumptionissuedependencydescriptionstringoptionalWhat it is, as HTML.
categorystringoptionalThe area of the project it touches; other by default.
technicalschedulescoperesourcebudgetexternalsecuritycompliancequalityotherprobabilityintegeroptionalHow likely, 1 to 5; risks only.
impactintegeroptionalHow bad, 1 to 5; risks and issues.
mitigationstringoptionalWhat makes it less likely or less bad, as HTML; risks only.
contingencystringoptionalWhat happens if it occurs, as HTML; risks only.
owner_idstringoptionalUUID of the person who answers for it.
due_onstringoptionalWhen it must be resolved, YYYY-MM-DD; issues and dependencies.
review_onstringoptionalWhen it is next reviewed, YYYY-MM-DD; risks and assumptions.
depends_onstringoptionalWhat the project depends on, in words; dependencies only.
statusstringoptionalWhere the item stands; a move the lifecycle allows.
openmonitoringmitigatingresolvedclosedoccurredacceptedWhat it returns
{ "data": { "id": "c9d0e1f2-a3b4-4c5d-8e6f-7a8b9c0d1e2f", "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "number": 3, "reference": "SCL-RSK-3", "type": "issue", "title": "The gateway sandbox is not approved yet", "description": "<p>Approved on the second application; keys arrived on the 3rd.</p>", "category": "external", "probability": null, "impact": 4, "score": null, "mitigation": null, "contingency": null, "owner_id": "3f8a1c2e-7b4d-4e5f-9a6b-1c2d3e4f5a6b", "owner_name": "Pat Manager", "raised_by": "5b6c7d8e-9f0a-4b1c-8d2e-3f4a5b6c7d8e", "raised_by_name": "Bea Analyst", "due_on": "2026-11-15", "review_on": null, "depends_on": null, "status": "resolved", "position": 3, "created_at": "2026-10-28T11:00:00+00:00", "updated_at": "2026-11-03T09:30:00+00:00" }}How it fails
VALIDATION_FAILEDa field outside its limits, a value outside its set, a rating outside 1 to 5, a move the lifecycle does not allow from where the item stands, or an owner_id who is not on the team.
RESOURCE_NOT_FOUNDunknown raid_item_id, or an item 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 raid:update.
TOKEN_MISSING_ABILITYtoken lacks raid:update.
How is this guide?
Last updated on