ha_bundle_export
Assembles a §27.6 haEvidenceBundle from a subject's collected human_accountability_records[] (reviewers, approvers, annotations, exception rationale, timestamps) -- same algorithm as the browser verify.html HA export card (kernels/_haevidence.mjs). Set sd_jwt:true to also export it as a Selective...
This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/ha-bundle-export.md
What ha_bundle_export does on Ainumbers Mcp Apps
AI agents use ha_bundle_export to create or update resources in Ainumbers Mcp Apps, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ainumbers Mcp Apps environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
sd_jwt | boolean | — | When true, also return an SD-JWT export of the bundle (default false). |
records | array | — | human_accountability_records over this subject. Default: []. |
input_hashes | array | — | sha256: hashes of the inputs the verification ran over. Default: []. |
subject_hash | string | Yes | Required. The sha256: subject hash the bundle documents. |
kernel_version | string | — | Version tag of the kernel that produced verification_result. |
policy_version | string | — | Version tag of the policy the kernel was evaluated against. |
submission_receipt | string | — | Populate ONLY after a real transmission -- never fabricate. |
verification_result | string | — | The §16/§18/§20 verdict. |
Parameters from the server's own tool schema.
Why ha_bundle_export is rated Medium
An AI agent can call ha_bundle_export faster than any human can review: one bad instruction and it creates or modifies resources in Ainumbers Mcp Apps by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs ha_bundle_export 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_bundle_export, this is the rule to start with:
ha_bundle_export stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_bundle_export call is checked against it from then on.
Questions about ha_bundle_export
Assembles a §27.6 haEvidenceBundle from a subject's collected human_accountability_records[] (reviewers, approvers, annotations, exception rationale, timestamps) -- same algorithm as the browser verify.html HA export card (kernels/_haevidence.mjs). Set sd_jwt:true to also export it as a Selective Disclosure JWT (§13.12), signed EdDSA over a fresh ephemeral did:key (generated per call, never reused) -- subject_hash/verification_result/kernel_version/policy_version/timestamps/submission_receipt are always-disclosed; reviewers/approvers/annotations/exception_rationale/input_hashes are selectively disclosable. It is categorised as a Write tool in the Ainumbers Mcp Apps MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
ha_bundle_export accepts 8 parameters: sd_jwt, records, input_hashes, subject_hash, kernel_version, policy_version, submission_receipt, verification_result. Required: 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_bundle_export: 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_bundle_export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ha_bundle_export 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_bundle_export. 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_bundle_export 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