Verify if an address owns a specific NFT
AI agents call verify-nft-ownership to retrieve information from Xrpl mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only verification of NFT ownership on the XRP Ledger. It retrieves and checks data (ownership status) but produces no side effects, no state changes, and no irreversible actions. It falls squarely within the Read category. Severity is low because misuse would only expose or confirm existing public ledger data about NFT ownership, with no financial impact or destructive capability.
From the tool's definition Tool name 'verify-nft-ownership' and description 'Verify if an address owns a specific NFT' indicate a query operation that checks ownership status without modifying data, triggering transactions, or executing arbitrary code.
Documented attack patterns abuse exactly the kind of access verify-nft-ownership gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Xrpl mcp, and nothing reaches the server without passing your rules. This is the rule we recommend for verify-nft-ownership:
{
"version": "1",
"default": "deny",
"tools": {
"verify-nft-ownership": {}
}
} verify-nft-ownership is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Verify if an address owns a specific NFT. It is categorised as a Read tool in the Xrpl mcp MCP Server, which means it retrieves data without modifying state.
Register the Xrpl MCP server in PolicyLayer and add a rule for verify-nft-ownership: 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 Xrpl mcp. Nothing to install.
verify-nft-ownership 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 verify-nft-ownership 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 verify-nft-ownership. 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.
verify-nft-ownership is provided by the Xrpl MCP server (romthpt/mcp-xrpl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Xrpl mcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
71 Xrpl mcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.