Tempo Stablecoin Issuance Compliance — OpenChainGraph compute node (compliance_mandate). Runs deterministically in-browser; zero PII, zero egress. Exports an AP2 artifact with execution_hash for chain provenance. Consumes upstream artifacts from: art-34-tempo-fit-diagnostic. Output feeds: art-06-...
AI agents call validate_tempo_token_compliance to retrieve information from Ainumbers Mcp Apps without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
compute | string | — | Compute mode (v0.4 Compute Binding). "auto" (default) = server for gpu:false nodes with registered kernels; "server" = force server-side; "browser" = always ret |
parent_hashes | array | — | execution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export). |
parent_tool_ids | array | — | tool_id values matching parent_hashes, in the same order. |
policy_parameters | object | — | Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is "auto" or "serv |
Parameters from the server's own tool schema.
This tool performs compliance validation and attestation—a read-like operation that checks state against rules and generates audit artifacts. While it outputs an AP2 artifact with execution_hash, this is a deterministic computation result for compliance reporting, not a write that creates mutable data or financial records.
From the tool's definition Tool description indicates it 'runs deterministically in-browser; zero PII, zero egress' and 'validates' compliance. No language indicating creation, modification, deletion, execution of external commands, or financial transactions.
Attacks that exploit this kind of access
Tempo Stablecoin Issuance Compliance — OpenChainGraph compute node (compliance_mandate). Runs deterministically in-browser; zero PII, zero egress. Exports an AP2 artifact with execution_hash for chain provenance. Consumes upstream artifacts from: art-34-tempo-fit-diagnostic. Output feeds: art-06-genius-act-reserve-attestation, art-10-amla-transaction-typology-risk-scorer, art-38-tempo-onchain-aml. Open at: https://ainumbers.co/chaingraph/art-37-tempo-stablecoin-issuance.html. It is categorised as a Read tool in the Ainumbers Mcp Apps MCP Server, which means it retrieves data without modifying state.
validate_tempo_token_compliance accepts 4 parameters: compute, parent_hashes, parent_tool_ids, 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_tempo_token_compliance: 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_tempo_token_compliance 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_tempo_token_compliance 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_tempo_token_compliance. 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_tempo_token_compliance 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →