build_disclosure_manifest
Builds a Merkle-rooted disclosure manifest from a caller-supplied digest list (DATAROOM-1-BUILD-SPEC.md §DR-4) -- the agent hashes files itself and passes {path,size,digest,content_type} entries; the worker never sees file contents. Same leaf scheme as tools/546-disclosure-manifest-builder.html: ...
This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/build-disclosure-manifest.md
What build_disclosure_manifest does on Ainumbers Mcp Apps
AI agents invoke build_disclosure_manifest to trigger actions in Ainumbers Mcp Apps. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
entries | array | Yes | List of {path,size,digest,content_type} -- the caller has already hashed each file. |
room_label | string | — | Label for the disclosure room. |
Parameters from the server's own tool schema.
Why build_disclosure_manifest is rated High
This tool executes a cryptographic computation (Merkle tree construction with specific leaf hashing scheme) over caller-supplied data and returns a computed artifact. It is not a simple read/query, nor does it write/store data persistently (signing and anchoring are explicitly deferred to the client). It runs a defined algorithm producing a new derived object, placing it in Execute.
From the tool's definition 'Builds a Merkle-rooted disclosure manifest from a caller-supplied digest list' and 'the worker never sees file contents' — it performs a deterministic computation (hashing, Merkle tree construction) over supplied inputs and returns a structured manifest…
Risk signalsAccepts file system path (entries[].path) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs build_disclosure_manifest 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_disclosure_manifest, this is the rule to start with:
build_disclosure_manifest stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 build_disclosure_manifest call is checked against it from then on.
Questions about build_disclosure_manifest
Builds a Merkle-rooted disclosure manifest from a caller-supplied digest list (DATAROOM-1-BUILD-SPEC.md §DR-4) -- the agent hashes files itself and passes {path,size,digest,content_type} entries; the worker never sees file contents. Same leaf scheme as tools/546-disclosure-manifest-builder.html: sha256(path|digest|size), duplicate-last-leaf on an odd level. Entries are sorted by path before hashing so the root is order-independent. Returns the manifest object + merkle_root; sign and anchor it client-side (or via a separate §16 signing step) if a signed artifact is required. It is categorised as a Execute tool in the Ainumbers Mcp Apps MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
build_disclosure_manifest accepts 2 parameters: entries, room_label. Required: entries. 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 build_disclosure_manifest: 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.
build_disclosure_manifest is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_disclosure_manifest 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 build_disclosure_manifest. 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.
build_disclosure_manifest 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.
Across the catalogue