READ

list_business_rules

A project's business rules in the project's order, with reference, name, kind, statement, condition and action, examples, authority, priority, dates in force, status and owner, narrowed for a guest token.

Return the business rules of one project: the decisions of the business the system must honour, each with its reference (such as CRM-BR-7), name, kind (a constraint, a derivation, a computation, an inference, an action enabler or a policy), the rule in plain words, when it applies and what follows, the exceptions, worked examples of an input and what is expected, who has the authority to change it, its MoSCoW priority, the dates it is in force, its status and owner. Read it before you implement a calculation, a validation or a decision, so the code follows the rule the business agreed rather than a guess, and name rules by their reference when you report.

Optional filters narrow the page to one type, one status, one priority, one owner_id or the rules whose reference, name or authority contain search. A guest token reads the agreed rules only (approved or baselined).

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.

Annotations

Read-only

It reads and never changes anything.

Arguments

project_id*string

UUID of the project whose rules to list.

typestringoptional

Narrow to one kind.

constraintderivationcomputationinferenceaction_enablerpolicy
statusstringoptional

Narrow to one status.

draftin_reviewapprovedbaselineddeprecated
prioritystringoptional

Narrow to one MoSCoW priority.

mustshouldcouldwont
owner_idstringoptional

Narrow to the rules one person answers for, by user UUID.

searchstringoptional

Words the reference, the name or the authority must contain.

limitintegeroptional

Rules per page (1..100, default 25).

min1max100
pageintegeroptional

1-indexed page number.

min1

What it returns

{  "data": [    {      "id": "d5e6f7a8-b9c0-4d1e-8f2a-3b4c5d6e7f80",      "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",      "number": 7,      "reference": "CRM-BR-7",      "name": "Platinum tier threshold",      "type": "inference",      "statement": "<p>A member whose spend over the last twelve months reaches 5,000 is a platinum member.</p>",      "condition": "When a member's rolling twelve-month spend reaches 5,000",      "action": "then the member moves to the platinum tier on the first of the next month",      "exceptions": "<p>Spend refunded within thirty days does not count.</p>",      "examples": [        { "input": "Spend 4,999 on 30 November", "expected": "Stays gold" },        {          "input": "Spend 5,000 on 30 November",          "expected": "Platinum from 1 December"        }      ],      "authority_stakeholder_id": "d6e7f8a9-b0c1-4d2e-9f3a-4b5c6d7e8f90",      "authority_stakeholder_name": "Amal Jayasuriya",      "authority": "Loyalty programme terms, section 4",      "priority": "must",      "effective_from": "2027-01-01",      "effective_to": null,      "status": "approved",      "owner_id": "c3d4e5f6-a7b8-4c9d-8e0f-1a2b3c4d5e6f",      "owner_name": "Nimal Fernando",      "position": 6,      "version": 0,      "approved_at": "2026-11-05T15:00:00+00:00",      "approved_revision_id": null,      "created_at": "2026-10-28T09:20:00+00:00",      "updated_at": "2026-11-05T15:00:00+00:00"    }  ],  "meta": { "page": 1, "limit": 25, "total": 1, "has_more": false }}

How it fails

RESOURCE_NOT_FOUND

unknown project_id, or a project outside the token's scope or the person's visibility.

VALIDATION_FAILED

type, status or priority is not one of its values.

TOKEN_MISSING_ABILITY

token lacks business-rule:view-any.

How is this guide?

Last updated on