build_evidence_pack

SERVERAinumbers Mcp Apps SOURCEpostoaklabs/ainumbers-mcp-apps

Low RISK CLASS

Category Read

Parameters 111 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/build-evidence-pack.md

WHAT IT DOES

What build_evidence_pack does on Ainumbers Mcp Apps

AI agents call build_evidence_pack 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
`sd_jwt`	boolean	—	When true, also return an SD-JWT export of the HA bundle (mirrors ha_bundle_export, default false; no-op when ha_records is absent).
`framing`	string	—	Optional framing context for the session receipt's PTG-01 regulator prompt.
`artifacts`	array	Yes	Already-produced artifacts this pack documents, in call order.
`ha_records`	array	—	§27 human_accountability_records -- omit entirely for no HA section.
`room_label`	string	—	Label for the disclosure-manifest room.
`session_id`	string	—	Session identifier to embed in the receipt, if the caller tracks one.
`subject_hash`	string	—	The sha256: subject hash the pack documents (defaults to artifacts[0].execution_hash if omitted).
`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 (same rule as ha_bundle_export).
`verification_result`	string	—	The §16/§18/§20 verdict.

Parameters from the server's own tool schema.

RISK

Why build_evidence_pack is rated Low

Aggregates and formats existing artifacts into a pack; no data modification or external side effects.

From the tool's definition Composes session receipt, evidence bundle, disclosure manifest from already-produced artifacts

Risk signalsHigh parameter count (14 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs build_evidence_pack 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 build_evidence_pack, this is the rule to start with:

build_evidence_pack Allowed

build_evidence_pack is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "build_evidence_pack": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ainumbers Mcp Apps, apply this rule, and every build_evidence_pack call is checked against it from then on.

FAQ

Questions about build_evidence_pack

What does the build_evidence_pack tool do? +

Composes a session receipt (build_session_receipt logic), an optional §27.6 HA evidence bundle (ha_bundle_export logic, included only when ha_records is supplied and non-empty), and a disclosure manifest (build_disclosure_manifest logic) from one array of already-produced artifacts, all keyed to the same input hashes -- replacing what today takes 4-6 separate tool calls with hand-carried hashes. Calls the same in-process functions those standalone tools use; if any one section fails to build, the whole call fails isError:true with that section's own message -- no partial pack. It is categorised as a Read tool in the Ainumbers Mcp Apps MCP Server, which means it retrieves data without modifying state.

What parameters does build_evidence_pack accept? +

build_evidence_pack accepts 11 parameters: sd_jwt, framing, artifacts, ha_records, room_label, session_id, subject_hash, kernel_version, policy_version, submission_receipt, verification_result. Required: artifacts. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on build_evidence_pack? +

Register the Ainumbers Mcp Apps MCP server in PolicyLayer and add a rule for build_evidence_pack: 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.

What risk level is build_evidence_pack? +

build_evidence_pack is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit build_evidence_pack? +

Yes. Add a rate_limit block to the build_evidence_pack 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.

How do I block build_evidence_pack completely? +

Set action: deny in the PolicyLayer policy for build_evidence_pack. 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.

What MCP server provides build_evidence_pack? +

build_evidence_pack 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.

KEEP EXPLORING

More on Ainumbers Mcp Apps, and thousands of servers like it.

This server

All 689 Ainumbers Mcp Apps tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →