validate_input_attestations
Verify an artifact's input_attestations[] (ChainGraph Standard §23): per RFC 6901 pointer, checks the attested value resolves inside policy_parameters and its digest binding matches, then verifies each type along its own path -- vc-2.0 via the shipped §16/§13.11 Data Integrity proof, rfc3161-snap...
This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/validate-input-attestations.md
What validate_input_attestations does on Ainumbers Mcp Apps
AI agents call validate_input_attestations 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 input_attestations[] and policy_parameters. |
policy_parameters | object | — | Artifact policy_parameters (if not passing a full artifact). |
input_attestations | array | — | The input_attestations[] array (if not passing a full artifact). |
Parameters from the server's own tool schema.
Why validate_input_attestations is rated Low
validate_input_attestations performs cryptographic and structural validation checks on existing attestation artifacts. It is purely informational—it queries and verifies data against policies but does not create, modify, delete, or execute arbitrary operations. The blast radius of misuse is limited to potential false verification results, a read-level impact.
From the tool's definition Tool description states it "Verify", "checks", and "verifies" attestations by resolving and matching values against policies and digests. Returns verification records without modifying data.
Attacks that exploit this kind of access
The rule that runs validate_input_attestations 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_input_attestations, this is the rule to start with:
validate_input_attestations 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_input_attestations call is checked against it from then on.
Questions about validate_input_attestations
Verify an artifact's input_attestations[] (ChainGraph Standard §23): per RFC 6901 pointer, checks the attested value resolves inside policy_parameters and its digest binding matches, then verifies each type along its own path -- vc-2.0 via the shipped §16/§13.11 Data Integrity proof, rfc3161-snapshot via the same §20 rfc3161-tst verifier (no second RFC 3161 implementation), c2pa-manifest structurally (hard-binding digest match), zktls structurally-only (reported verifiable:"external" -- OCG never treats it as confirmed). Returns one { pointer, type, structural, verifiable } record per entry. Pure client-safe compute, zero network. It is categorised as a Read tool in the Ainumbers Mcp Apps MCP Server, which means it retrieves data without modifying state.
validate_input_attestations accepts 3 parameters: artifact, policy_parameters, input_attestations. 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_input_attestations: 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_input_attestations 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_input_attestations 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_input_attestations. 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_input_attestations 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