validate_private_inputs
Verify an artifact's private_inputs[] (ChainGraph Standard §25 ocg-private-input@1) WITHOUT ever seeing the plaintext witness: per RFC 6901 pointer, checks the pointed value inside policy_parameters IS the declared sha256-salted@1 commitment (never the plaintext, §25.2), that the commitment schem...
This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/validate-private-inputs.md
What validate_private_inputs does on Ainumbers Mcp Apps
AI agents call validate_private_inputs 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 |
|---|---|---|---|
artifact | object | — | A full ChainGraph artifact envelope carrying private_inputs[], policy_parameters, and optionally output_payload + audit_signature.compute_proof. |
disclosures | array | — | OPTIONAL authorized-verifier disclosure packages, keyed by pointer, for the disclosed-verified path. |
compute_proof | object | — | audit_signature.compute_proof (if not passing a full artifact). |
output_payload | object | — | Artifact output_payload (if not passing a full artifact). |
private_inputs | array | — | The private_inputs[] array (if not passing a full artifact). |
policy_parameters | object | — | Artifact policy_parameters (if not passing a full artifact). |
Parameters from the server's own tool schema.
Why validate_private_inputs is rated Low
This tool only reads and validates existing cryptographic commitments and schema structures. It performs integrity checks and verification logic (comparing sha256 hashes, validating commitment schemes, confirming journal bindings) but does not create, modify, delete, or execute external code.
From the tool's definition Tool performs verification and checking operations: 'Verify', 'checks', 'confirm' — comparing cryptographic commitments and schemas without modification.
Attacks that exploit this kind of access
The rule that runs validate_private_inputs 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 validate_private_inputs, this is the rule to start with:
validate_private_inputs 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 validate_private_inputs call is checked against it from then on.
Questions about validate_private_inputs
Verify an artifact's private_inputs[] (ChainGraph Standard §25 ocg-private-input@1) WITHOUT ever seeing the plaintext witness: per RFC 6901 pointer, checks the pointed value inside policy_parameters IS the declared sha256-salted@1 commitment (never the plaintext, §25.2), that the commitment scheme is known, and -- when a §18 compute_proof is present -- that its journal commits the same commitment and binds output_payload. Optionally accepts an out-of-band {pointer, salt, input_value} disclosure package (authorized-verifier path) and recomputes sha256(salt || cgCanon(input_value)) to confirm it equals the commitment. Returns one {pointer, verifiable} record per entry: "proof-only" | "disclosed-verified" | "commitment-only" (no proof yet -- structural + plaintext-exclusion only) | "failed". Pure client-safe compute, zero network, never requires the plaintext. It is categorised as a Read tool in the Ainumbers Mcp Apps MCP Server, which means it retrieves data without modifying state.
validate_private_inputs accepts 6 parameters: artifact, disclosures, compute_proof, output_payload, private_inputs, policy_parameters. 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 validate_private_inputs: 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.
validate_private_inputs 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 validate_private_inputs 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 validate_private_inputs. 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.
validate_private_inputs 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