check_eudi_readiness

EUDI Wallet Credential-Acceptance Readiness Checker — OpenChainGraph compute node (compliance_mandate). Regulatory deadline: 2026-11 (EUDI Wallet member-state rollout November 2026; FI SCA acceptance December 2027; AMLR July 2027). Runs deterministically in-browser; zero PII, zero egress. Exports...

Server Ainumbers Mcp Apps postoaklabs/ainumbers-mcp-apps
Category Read
Risk class Low
Parameters 40 required

What check_eudi_readiness does on Ainumbers Mcp Apps

AI agents call check_eudi_readiness 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.

ParameterTypeRequiredDescription
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.

Why check_eudi_readiness needs a policy

This is a compliance assessment and audit tool. It evaluates an organization's readiness against regulatory requirements (EUDI Wallet adoption deadlines) and generates a report artifact. The tool reads/checks compliance status deterministically without creating, modifying, deleting data or executing external financial operations. It is Read category due to its query/assessment nature.

From the tool's definition Tool description explicitly states 'Readiness Checker' that 'Runs deterministically in-browser; zero PII, zero egress.' It retrieves and evaluates compliance readiness status for EUDI Wallet credentials against regulatory deadlines.

Questions about check_eudi_readiness

What does the check_eudi_readiness tool do? +

EUDI Wallet Credential-Acceptance Readiness Checker — OpenChainGraph compute node (compliance_mandate). Regulatory deadline: 2026-11 (EUDI Wallet member-state rollout November 2026; FI SCA acceptance December 2027; AMLR July 2027). Runs deterministically in-browser; zero PII, zero egress. Exports an AP2 artifact with execution_hash for chain provenance. Output feeds: art-04-agent-identity-attestation-checker, ptg-01-ap2-prompt-template-generator. Open at: https://ainumbers.co/chaingraph/art-13-eudi-wallet-credential-readiness-checker.html. It is categorised as a Read tool in the Ainumbers Mcp Apps MCP Server, which means it retrieves data without modifying state.

What parameters does check_eudi_readiness accept? +

check_eudi_readiness 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.

How do I enforce a policy on check_eudi_readiness? +

Register the Ainumbers Mcp Apps MCP server in PolicyLayer and add a rule for check_eudi_readiness: 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.

What risk level is check_eudi_readiness? +

check_eudi_readiness is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_eudi_readiness? +

Yes. Add a rate_limit block to the check_eudi_readiness 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.

How do I block check_eudi_readiness completely? +

Set action: deny in the PolicyLayer policy for check_eudi_readiness. 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.

What MCP server provides check_eudi_readiness? +

check_eudi_readiness 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.