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...
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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.
Attacks that exploit this kind of access
The rule that runs get_pending_offers 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 get_pending_offers, this is the rule to start with:
get_pending_offers 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 get_pending_offers call is checked against it from then on.
Questions about 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 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.
get_pending_offers accepts 1 parameter: address. Required: address. 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 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.
get_pending_offers 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 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.
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.
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.
This server
Across the catalogue