ha_record_validate
Structural (non-cryptographic) §27.2 signed-named-human check: does this record carry a §16 whole-artifact proof (eddsa-jcs-2022) whose verificationMethod is bound to the record's own identity.id? Does NOT verify the signature bytes -- pair with verify_execution_hash / a proof verifier for that. ...
This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/ha-record-validate.md
What ha_record_validate does on Ainumbers Mcp Apps
AI agents call ha_record_validate 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 |
|---|---|---|---|
record | object | Yes | A single human_accountability_records[] entry to check. |
Parameters from the server's own tool schema.
Why ha_record_validate is rated Low
This is a read-only validation/inspection tool. It examines cryptographic record structures to determine if they meet proof-of-identity requirements, returning a boolean-like judgment without side effects. The server description emphasizes 'Read-only, no auth, zero PII' context.
From the tool's definition Tool performs structural validation checks (§27.2 signed-named-human check, eddsa-jcs-2022 proof structure) without executing transactions, modifying data, or moving funds.
Attacks that exploit this kind of access
The rule that runs ha_record_validate 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_record_validate, this is the rule to start with:
ha_record_validate 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_record_validate call is checked against it from then on.
Questions about ha_record_validate
Structural (non-cryptographic) §27.2 signed-named-human check: does this record carry a §16 whole-artifact proof (eddsa-jcs-2022) whose verificationMethod is bound to the record's own identity.id? Does NOT verify the signature bytes -- pair with verify_execution_hash / a proof verifier for that. Use before counting a record toward ha_gate_status. It is categorised as a Read tool in the Ainumbers Mcp Apps MCP Server, which means it retrieves data without modifying state.
ha_record_validate accepts 1 parameter: record. Required: record. 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_record_validate: 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_record_validate 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_record_validate 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_record_validate. 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_record_validate 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