spraay_kyc_status

Check KYC verification status by record ID or wallet address. Returns verification level, check results, and expiry. Data persists in Supabase. Costs $0.005 USDC.

SERVERSpraay X402 Mcp SOURCEspraay-x402-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-plagtech-spraay-x402-mcp/spraay-kyc-status.md

WHAT IT DOES

What spraay_kyc_status does on Spraay X402 Mcp

AI agents call spraay_kyc_status to retrieve information from Spraay X402 Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why spraay_kyc_status is rated Low

This tool performs a read-only lookup of KYC status information. Although it operates in a crypto/DeFi context and incurs a small cost, it neither moves funds, modifies records, executes transactions, nor deletes data. The cost is a query fee, not a financial transaction that commits obligations. The primary action is information retrieval, placing it firmly in the Read category with low severity.

From the tool's definition 'Check KYC verification status' is a query operation that retrieves existing verification data; 'Returns verification level, check results, and expiry' confirms data retrieval with no modification, deletion, or execution of code/transactions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs spraay_kyc_status safely

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

spraay_kyc_status Allowed

spraay_kyc_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "spraay_kyc_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about spraay_kyc_status

What does the spraay_kyc_status tool do? +

Check KYC verification status by record ID or wallet address. Returns verification level, check results, and expiry. Data persists in Supabase. Costs $0.005 USDC. It is categorised as a Read tool in the Spraay X402 Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on spraay_kyc_status? +

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

What risk level is spraay_kyc_status? +

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

Can I rate-limit spraay_kyc_status? +

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

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

spraay_kyc_status is provided by the Spraay X402 MCP server (spraay-x402-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Spraay X402, and thousands of servers like it.

This server

All 183 Spraay X402 tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →