verify_disclosure_inclusion
Proves (or refutes) that a {path,digest} pair was in a disclosure manifest's room (DATAROOM-1-BUILD-SPEC.md §DR-4) -- worker-side mirror of tools/547-disclosure-manifest-verifier.html's single-file inclusion check. Recomputes the manifest's Merkle root over its entries[], builds the inclusion pro...
This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/verify-disclosure-inclusion.md
What verify_disclosure_inclusion does on Ainumbers Mcp Apps
AI agents call verify_disclosure_inclusion 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 |
|---|---|---|---|
path | string | Yes | Path of the entry to prove. |
digest | string | Yes | sha256:-prefixed digest of the file to prove. |
manifest | object | Yes | The disclosure manifest to check against (needs entries[] + merkle_root). |
Parameters from the server's own tool schema.
Why verify_disclosure_inclusion is rated Low
This tool performs cryptographic verification of manifest inclusion by recomputing and validating Merkle proofs. It has no side effects beyond returning a boolean verification result. The operation is deterministic, non-mutating, and purely informational. While it involves complex cryptographic operations, it does not execute arbitrary code, create/modify/delete data, or involve financial transactions.
From the tool's definition Proves (or refutes) that a {path,digest} pair was in a disclosure manifest -- verifies inclusion via Merkle proof recomputation; no data creation, modification, deletion, or financial operations. Described as 'read-only' in server description.
Risk signalsAccepts file system path (path) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs verify_disclosure_inclusion 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 verify_disclosure_inclusion, this is the rule to start with:
verify_disclosure_inclusion 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 verify_disclosure_inclusion call is checked against it from then on.
Questions about verify_disclosure_inclusion
Proves (or refutes) that a {path,digest} pair was in a disclosure manifest's room (DATAROOM-1-BUILD-SPEC.md §DR-4) -- worker-side mirror of tools/547-disclosure-manifest-verifier.html's single-file inclusion check. Recomputes the manifest's Merkle root over its entries[], builds the inclusion proof path for the target entry, and reapplies it to confirm it reduces to the claimed merkle_root. Absence is only provable against the exact manifest version passed in. It is categorised as a Read tool in the Ainumbers Mcp Apps MCP Server, which means it retrieves data without modifying state.
verify_disclosure_inclusion accepts 3 parameters: path, digest, manifest. Required: path, digest, manifest. 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 verify_disclosure_inclusion: 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.
verify_disclosure_inclusion 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 verify_disclosure_inclusion 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 verify_disclosure_inclusion. 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.
verify_disclosure_inclusion 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