create_raid_item
Adds any entry of the RAID log, an assumption, an issue or a dependency as well as a risk; the full form beside raise_risk.
Add an item to a project's RAID log: project_id and title are required; type is risk by default or one of assumption, issue, dependency; description (HTML), category, probability and impact (1 to 5; probability on a risk, impact on a risk or an issue), mitigation and contingency (HTML, risks), owner_id, due_on (issues and dependencies), review_on (risks and assumptions), depends_on (what the project leans on, in words, dependencies) and status (open by default) fill in the rest; the columns a kind does not carry are dropped. The item takes the next number of the RAID sequence, names the person you act for as the one who raised it and is announced as raid_item.created.
raise_risk remains the short road for a risk. A staff token with raid:create 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.
Annotations
A client that honours annotations asks a person before running it.
Arguments
project_id*stringUUID of the project.
title*stringWhat 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.
What 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>The payment provider has not issued sandbox keys; the checkout cannot be tested end to end.</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": "open", "position": 3, "created_at": "2026-10-28T11:00:00+00:00", "updated_at": "2026-10-28T11:00:00+00:00" }}How it fails
VALIDATION_FAILEDtitle missing or outside 3 to 200 characters, a type, category or status outside its set, a rating outside 1 to 5, a date that is not YYYY-MM-DD, or an owner_id who is not on the team.
RESOURCE_NOT_FOUNDunknown project_id, or a project 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:create.
TOKEN_MISSING_ABILITYtoken lacks raid:create.
How is this guide?
Last updated on