raise_risk
Raise a risk in a project's RAID log, numbered from the log's sequence, scored by probability and impact, raised by the person the token acts as and open for the review meeting.
Add a risk to a project's RAID log: title (required), description, category (the area it touches, other by default), probability and impact (one to five, how likely and how bad), mitigation (what makes it less likely or less bad) and contingency (what happens if it occurs). The risk takes the next number of the log's sequence (CRM-RSK-4), starts open, records the person the token acts as as its raiser, writes its first version and goes out as raid_item.created. Raise a risk when a story, a plan or a conversation shows something that may go wrong and nothing records it yet; say how likely and how bad it is, and what the team can do about it, so the review meeting can act on it.
Only a risk is raised here. An issue, an assumption or a dependency is a person's call on the RAID Log page or over the REST API, and so are changing, moving and deleting items.
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.
Arguments
project_id*stringUUID of the project whose log the risk joins.
title*stringWhat the risk is called, 3 to 200 characters.
descriptionstringoptionalWhat may happen and why it would hurt, as HTML.
categorystringoptionalThe area of the project it touches; other by default.
technicalschedulescoperesourcebudgetexternalsecuritycompliancequalityotherprobabilityintegeroptionalHow likely, from one (rare) to five (almost certain).
1max5impactintegeroptionalHow bad, from one (negligible) to five (severe).
1max5mitigationstringoptionalWhat makes it less likely or less bad, as HTML.
contingencystringoptionalWhat happens if it occurs, as HTML.
What it returns
{ "data": { "id": "f7a8b9c0-d1e2-4f3a-8b4c-5d6e7f8a9b02", "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "number": 4, "reference": "CRM-RSK-4", "type": "risk", "title": "Payment provider sandbox may lag behind production", "description": "<p>The provider ships new card flows to production weeks before its sandbox.</p>", "category": "external", "probability": 3, "impact": 4, "score": 12, "mitigation": "<p>Run the checkout smoke test against the provider's production account every Monday.</p>", "contingency": null, "owner_id": null, "owner_name": null, "raised_by": "d4e5f6a7-b8c9-4d0e-9f1a-2b3c4d5e6f70", "raised_by_name": "Sithara Perera", "due_on": null, "review_on": null, "depends_on": null, "status": "open", "position": 3, "created_at": "2026-10-28T09:20:00+00:00", "updated_at": "2026-10-28T09:20:00+00:00" }}How it fails
RESOURCE_NOT_FOUNDunknown project_id, or a project outside the token's scope or the person's visibility.
VALIDATION_FAILEDtitle is missing or longer than 200 characters, a rating is outside one to five, or category is not one of its values.
FORBIDDENthe person's role on the project does not carry raid:create, or the token is a client guest's.
TOKEN_MISSING_ABILITYtoken lacks raid:create.
How is this guide?
Last updated on