get-token-metadata

Get token metadata (name, symbol, decimals, supply)

SERVERXrpl mcp SOURCEromthpt/mcp-xrpl

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/romthpt-mcp-xrpl/get-token-metadata.md

WHAT IT DOES

What get-token-metadata does on Xrpl mcp

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

RISK

Why get-token-metadata is rated Low

This tool only reads and returns immutable metadata about tokens on the XRP Ledger. It does not create, modify, delete, or transfer any data or assets. The blast radius of misuse is minimal—an AI agent obtaining token metadata poses negligible security risk.

From the tool's definition The tool description states it retrieves token metadata (name, symbol, decimals, supply). These are passive query operations with no side effects or state modifications. The function name 'get-' prefix also indicates a retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get-token-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-token-metadata, this is the rule to start with:

get-token-metadata Allowed

get-token-metadata is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-token-metadata": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Xrpl mcp, apply this rule, and every get-token-metadata call is checked against it from then on.

FAQ

Questions about get-token-metadata

What does the get-token-metadata tool do? +

Get token metadata (name, symbol, decimals, supply). It is categorised as a Read tool in the Xrpl mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-token-metadata? +

Register the Xrpl MCP server in PolicyLayer and add a rule for get-token-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.

What risk level is get-token-metadata? +

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

Can I rate-limit get-token-metadata? +

Yes. Add a rate_limit block to the get-token-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.

How do I block get-token-metadata completely? +

Set action: deny in the PolicyLayer policy for get-token-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.

What MCP server provides get-token-metadata? +

get-token-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.

KEEP EXPLORING

More on Xrpl, and thousands of servers like it.

This server

All 71 Xrpl tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →