check_order_status
Check the backend order status for a domain you tried to register on xrpdomains.xyz. Returns whether payment landed, the offer was created, the mint completed, or it failed at a step. Use when a user asks "did my X.xrp registration go through?" or "what's the status of my order?". This is deeper ...
This record as markdown: /tools/io-github-xrpdomains-xrpname-mcp-server/check-order-status.md
What check_order_status does on XRPName
AI agents call check_order_status to retrieve information from XRPName 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 |
|---|---|---|---|
domain | string | Yes | The domain whose order to check, e.g. "alice.xrp". |
Parameters from the server's own tool schema.
Why check_order_status is rated Low
Queries registration status without modifying data or triggering transactions.
From the tool's definition Check backend order status, returns payment, offer, mint, or failure.
Attacks that exploit this kind of access
The rule that runs check_order_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and XRPName, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_order_status, this is the rule to start with:
check_order_status 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 XRPName, apply this rule, and every check_order_status call is checked against it from then on.
Questions about check_order_status
Check the backend order status for a domain you tried to register on xrpdomains.xyz. Returns whether payment landed, the offer was created, the mint completed, or it failed at a step. Use when a user asks "did my X.xrp registration go through?" or "what's the status of my order?". This is deeper than check_domains (which only shows availability). It is categorised as a Read tool in the XRPName MCP Server, which means it retrieves data without modifying state.
check_order_status accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the XRPName MCP server in PolicyLayer and add a rule for check_order_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 XRPName. Nothing to install.
check_order_status 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 check_order_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.
Set action: deny in the PolicyLayer policy for check_order_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.
check_order_status is provided by the XRPName MCP server (@xrpname/xrpname-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on XRPName, and thousands of servers like it.
This server
Across the catalogue