This record as markdown: /tools/romthpt-mcp-xrpl/get-nft-metadata.md
What get-nft-metadata does on Xrpl mcp
AI agents call get-nft-metadata 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-metadata is rated Low
This tool queries and retrieves NFT metadata from the XRP Ledger without modifying, deleting, or executing any transactions. It is a read-only operation that returns information about NFT collections and tokens, consistent with the Read category for data retrieval operations.
From the tool's definition Tool is named 'get-nft-metadata' and described as 'Get NFT collection and token metadata'. The verb 'Get' and the phrase 'metadata' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get-nft-metadata 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-metadata, this is the rule to start with:
get-nft-metadata 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-metadata call is checked against it from then on.
Questions about get-nft-metadata
Get NFT collection and token metadata. 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-metadata: 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-metadata 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-metadata 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-metadata. 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-metadata 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