> For the complete documentation index, see [llms.txt](https://vayl.gitbook.io/vayl-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vayl.gitbook.io/vayl-docs/documentation/mcp-tools/safety-and-gating.md). # Safety and gating Guardrails for high-stakes agents. See the [Safety gates guide](/vayl-docs/documentation/guides/safety-gates-and-human-approval.md) for the workflow. A `?` marks an optional argument. ## check\_before\_act ```python check_before_act(subject, user_id?, agent_id?, run_id?, min_confidence?, require_active?, block_on_flagged?, max_staleness_days?, block_on_recent_change_days?) ``` A safety gate to call **before** an irreversible action. Returns **SAFE**, or **BLOCKED** with reasons. | Argument | Description | | ----------------------------- | --------------------------------------------- | | `subject` | the slot you're about to act on | | `min_confidence` | minimum confidence to be considered safe | | `require_active` | require a current (non-retired) value | | `block_on_flagged` | block if the value is disputed/flagged | | `max_staleness_days` | reject facts older than this | | `block_on_recent_change_days` | block if the value changed within this window | **Example** ```json {"name": "check_before_act", "arguments": {"subject": "active_medication", "user_id": "patient_42", "block_on_flagged": true}} ``` ``` ✅ SAFE to act on 'active_medication'. current: active_medication = warfarin 7 mg PO daily ``` When a value is disputed, stale, or below the confidence bar, the same call returns: ``` ⛔ BLOCKED — do NOT act on 'active_medication': • value is flagged (unresolved conflict) ``` ## safe\_recall ```python safe_recall(question, user_id?, agent_id?, run_id?, min_confidence?, require_active?, block_on_flagged?, max_staleness_days?, block_on_recent_change_days?, critical_categories?) ``` Like `recall`, but answers **only if** every current fact behind the answer passes the same policy checks as `check_before_act`; otherwise it withholds the answer and returns why. Use it on the path to an action. ## pending\_changes ```python pending_changes(user_id?, agent_id?, run_id?) ``` Show proposed changes to **confirm-required** slots that haven't been applied — the human-approval queue. Each entry shows old to new and the sentence that triggered it. ## confirm\_change ```python confirm_change(memory_id, user_id?, agent_id?, run_id?, decided_by?) ``` Approve a proposed change, applying it. Records **who** decided (`decided_by`). A proposal can't be confirmed if the value it would replace has since changed. ## reject\_change ```python reject_change(memory_id, user_id?, agent_id?, run_id?, decided_by?) ``` Discard a proposed change. The current value stands; the proposal is kept as history. ## set\_reconcile\_policy ```python set_reconcile_policy(mode?, authority?, user_id?, agent_id?, run_id?) ``` Configure how a **shared** space resolves conflicts between contributors: | `mode` | Behaviour | | ----------- | ------------------------------------------------------------------ | | `RECENCY` | newer wins | | `AUTHORITY` | higher-ranked source wins; a lower one is flagged, not overwritten | | `REVIEW` | every cross-source conflict is flagged | `authority` maps a source to a rank, used by `AUTHORITY` mode. ## get\_reconcile\_policy ```python get_reconcile_policy(user_id?, agent_id?, run_id?) ``` Show the current reconciliation policy for the space. ## Next steps

:gear: Safety gates & human approval

The full workflow for gating writes and requiring approval./pages/d9d593aeabc52a165190bf8c93720491a4eb9682

:file-signature: Accountability

Record what the agent decided, on a signed audit chain./pages/R2NPTpA8ljGHbWMvp6xn

:database: Memory

The store-and-recall tools these gates protect./pages/atmh20zKFo3dWE6nALWX
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://vayl.gitbook.io/vayl-docs/documentation/mcp-tools/safety-and-gating.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.