auth_wallet_challenge

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Critical RISK CLASS

Category Financial

Parameters 31 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/auth-wallet-challenge.md

WHAT IT DOES

What auth_wallet_challenge does on Rokha

AI agents use auth_wallet_challenge to commit financial operations through Rokha, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`chain`	string	—	optional chain override (solana \| evm) — auto-detected from the address
`wallet_type`	string	—	defaults by address shape: 0x → metamask, else phantom
`wallet_address`	string	Yes	the wallet's public address (base58 Solana or 0x EVM)

Parameters from the server's own tool schema.

RISK

Why auth_wallet_challenge is rated Critical

Authentication flow leads to financial commitment; paid plan with USDC payment unlocks usage.

From the tool's definition paid plan — 7-day card trial or first month in USDC

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs auth_wallet_challenge safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For auth_wallet_challenge, this is the rule to start with:

auth_wallet_challenge Approval-gated

Any call to auth_wallet_challenge is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "auth_wallet_challenge": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every auth_wallet_challenge call is checked against it from then on.

FAQ

Questions about auth_wallet_challenge

What does the auth_wallet_challenge tool do? +

Step 1 of registering (or logging in) a user with a wallet keypair — no browser needed. Returns a challenge message to sign with the wallet's private key. Works for Solana (base58 Ed25519 address) and EVM (0x address). Follow with auth_wallet_verify. New wallets are auto-registered on first verify (a paid plan — 7-day card trial or first month in USDC — unlocks usage). It is categorised as a Financial tool in the Rokha MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does auth_wallet_challenge accept? +

auth_wallet_challenge accepts 3 parameters: chain, wallet_type, wallet_address. Required: wallet_address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on auth_wallet_challenge? +

Register the Rokha MCP server in PolicyLayer and add a rule for auth_wallet_challenge: 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 Rokha. Nothing to install.

What risk level is auth_wallet_challenge? +

auth_wallet_challenge is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit auth_wallet_challenge? +

Yes. Add a rate_limit block to the auth_wallet_challenge 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 auth_wallet_challenge completely? +

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

auth_wallet_challenge is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools → Critical-risk tools on this server →

Across the catalogue

export_wallet on Conviction → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →