Check a mandate for errors
validate_mandateCall this after writing or editing a mandate, before relying on it. Returns valid true or false with the reason: schema errors, clauses that can never run because an earlier clause already decides them, unbounded prefixes, credential material, and expiry. An invalid mandate makes every check_action call answer error. Once per mandate version is enough; there is no need to call it before every check_action. Free, and it keeps no request content. Docs: https://hanria.ai/llms.txt
Example tool call
This call uses example arguments supplied in the tool’s input schema.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"mandate": {
"clauses": [
{
"id": "permit-file",
"match": {
"kind": [
"file"
]
},
"effect": "permit"
}
],
"default": "deny",
"purpose": "Permit one file action.",
"mandate_id": "minimal-permit",
"schema_version": "0.2-draft"
}
},
"name": "validate_mandate"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mandate | Yes | An operator-authored statement of what an agent may do. Written by a person, read by an agent, evaluated locally. A mandate is advisory: it describes intended authority and supports a local check, but it does not enforce anything. Enforcement requires a component that exclusively holds the credentials and can refuse. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| valid | Yes | ||
| reason | Yes | ||
| clauses | No | ||
| expired | No | True when not_valid_after has passed; check_action then denies everything. | |
| mandate_ref | No | ||
| mandate_digest | No | SHA-256 of the mandate's canonical JSON; receipts carry the same value. | |
| schema_version | Yes |