Skip to content
Official MCP RegistryListed

ai.hanria/check

Check a proposed agent action against operator's rules: permit, deny or escalate, with the clause.

First seen 2 Oct 2026. Evidence as of 6 Oct 2026.

2
Tools
From an anonymous probe
1
Source listings
Each with its own history
4
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
check_actionCall this before your agent does something consequential (sends, pays, deletes, publishes, installs or changes access). Pass mandate (the operator's rules; the first matching clause decides) and action (kind, verb, target, optional counterparty and amount). Returns permit, deny or escalate with the governing clause, a reason, an action digest and a signed receipt; treat error as deny. Advisory: it cannot stop an action, and it keeps no request content. To check a new mandate first, call validate_mandate. Examples: inputSchema. Docs: https://hanria.ai/llms.txtRead-only
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.txtRead-only

Change history

  1. validate_mandate: input schema changed
  2. validate_mandate: description changed (+"Once per mandate version is enough; there is no need to call it before every check_action." +"Docs:" -"Documentation:")
  3. check_action: input schema changed
  4. check_action: description changed (+"access). Pass mandate (the operator's rules;" +"first matching clause decides) and" +"(kind, verb, target, optional counterparty and amount).")
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registryai.hanria/check2 Oct 20266 Oct 20261