This record as markdown: /tools/romthpt-mcp-xrpl/get-nft-collection.md
What get-nft-collection does on Xrpl mcp
AI agents call get-nft-collection to retrieve information from Xrpl mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get-nft-collection is rated Low
This tool retrieves NFT ownership information for a given address on the XRP Ledger. It performs a read-only query with no side effects, no code execution, no data modification, and no financial impact. The blast radius of misuse is minimal—an attacker could only enumerate NFT holdings, which may be considered sensitive but involves no destructive or financial harm.
From the tool's definition Tool name 'get-nft-collection' and description 'Get all NFTs owned by an address' indicate a query operation that retrieves data without modification or execution of transactions.
Attacks that exploit this kind of access
The rule that runs get-nft-collection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Xrpl mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-nft-collection, this is the rule to start with:
get-nft-collection 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 Xrpl mcp, apply this rule, and every get-nft-collection call is checked against it from then on.
Questions about get-nft-collection
Get all NFTs owned by an address. 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 get-nft-collection: 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.
get-nft-collection 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-nft-collection 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-nft-collection. 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-nft-collection 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.
More on Xrpl, and thousands of servers like it.
This server
Across the catalogue