New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_pending_offers

Get all pending XRPL domain operations for a wallet — incoming offers (someone offered the wallet a domain), outgoing offers (the wallet listed a domain), and paid-but-not-yet-minted orders the user can still complete. Use when the user asks "do I have any pending transfers?", "what offers are wa...

SERVERXRPName SOURCE@xrpname/xrpname-mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/io-github-xrpdomains-xrpname-mcp-server/get-pending-offers.md

What get_pending_offers does on XRPName

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

ParameterTypeRequiredDescription
address string Yes XRPL r... address of the wallet to query (e.g. "rPT1Sjq2YGrBMTttX4GZHjKu9dyfzbpAYe").

Parameters from the server's own tool schema.

Why get_pending_offers is rated Low

Retrieves pending offers and operations without modifying or deleting data; purely informational query.

From the tool's definition Get all pending XRPL domain operations for a wallet — retrieves incoming offers, outgoing offers, orders.

Questions about get_pending_offers

What does the get_pending_offers tool do? +

Get all pending XRPL domain operations for a wallet — incoming offers (someone offered the wallet a domain), outgoing offers (the wallet listed a domain), and paid-but-not-yet-minted orders the user can still complete. Use when the user asks "do I have any pending transfers?", "what offers are waiting on me?", or before suggesting an accept/cancel/continue-mint action. Requires an XRPL r... address. It is categorised as a Read tool in the XRPName MCP Server, which means it retrieves data without modifying state.

What parameters does get_pending_offers accept? +

get_pending_offers accepts 1 parameter: address. Required: address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_pending_offers? +

Register the XRPName MCP server in PolicyLayer and add a rule for get_pending_offers: 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.

What risk level is get_pending_offers? +

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

Can I rate-limit get_pending_offers? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of XRPName's. Pull the full record:

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.