ha_gate_status
Given a step's haGatePolicy and the human_accountability_records[] collected for a subject, returns whether the gate is satisfied, held, rejected, escalated, or overridden -- same algorithm as the browser verify.html HA gate card (kernels/_hagate.mjs, SPEC.md §27.4-27.5). A rejection record is te...
This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/ha-gate-status.md
What ha_gate_status does on Ainumbers Mcp Apps
AI agents call ha_gate_status to retrieve information from Ainumbers Mcp Apps without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
role | string | Yes | The haRole a satisfying approval record must carry. |
now_iso | string | Yes | Caller-supplied ISO 8601 clock (determinism; never Date.now() internally). |
records | array | — | Collected human_accountability_records over this subject. Default: []. |
threshold | integer | — | N for dual_control/review_required/hold. Default 1 (2 for dual_control). |
gate_policy | string | Yes | The step's declared haGatePolicy. |
subject_hash | string | Yes | The sealed artifact's sha256: subject hash. |
require_conformant | boolean | — | Require §27.2 structural signature shape on every record (default true). |
Parameters from the server's own tool schema.
Why ha_gate_status is rated Low
Despite its role in human accountability workflows, this tool only queries and evaluates state against policy—it retrieves and returns status information without altering data, executing code, or committing financial actions. The 'pure function' description confirms deterministic read-only behavior.
From the tool's definition Tool returns gate status (satisfied, held, rejected, escalated, or overridden) based on supplied inputs; described as 'pure function' with no side effects. No creation, modification, deletion, execution, or financial operations.
Attacks that exploit this kind of access
The rule that runs ha_gate_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ainumbers Mcp Apps, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ha_gate_status, this is the rule to start with:
ha_gate_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ainumbers Mcp Apps, apply this rule, and every ha_gate_status call is checked against it from then on.
Questions about ha_gate_status
Given a step's haGatePolicy and the human_accountability_records[] collected for a subject, returns whether the gate is satisfied, held, rejected, escalated, or overridden -- same algorithm as the browser verify.html HA gate card (kernels/_hagate.mjs, SPEC.md §27.4-27.5). A rejection record is terminal-blocking regardless of policy; an active time-boxed override (§27.5) takes precedence over the underlying policy. Pure function: caller supplies nowISO for determinism. It is categorised as a Read tool in the Ainumbers Mcp Apps MCP Server, which means it retrieves data without modifying state.
ha_gate_status accepts 7 parameters: role, now_iso, records, threshold, gate_policy, subject_hash, require_conformant. Required: role, now_iso, gate_policy, subject_hash. The full parameter table on this page comes from the server's own tool schema.
Register the Ainumbers Mcp Apps MCP server in PolicyLayer and add a rule for ha_gate_status: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Ainumbers Mcp Apps. Nothing to install.
ha_gate_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ha_gate_status rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for ha_gate_status. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
ha_gate_status is provided by the Ainumbers Mcp Apps MCP server (postoaklabs/ainumbers-mcp-apps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ainumbers Mcp Apps, and thousands of servers like it.
This server
Across the catalogue