Get detailed information about a token: price, market cap, volume, liquidity, and optionally a price chart. For just the USD price, use get_token_price instead — it
AI agents call get_token_details to retrieve information from Relay MCP Server 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 data retrieval operation. It fetches public blockchain token metadata and market data without creating, modifying, deleting, or executing any actions. The absence of side effects, combined with the informational nature of the returned data (price, market cap, volume, liquidity, charts), clearly places it in the Read category.
From the tool's definition Tool retrieves detailed token information including price, market cap, volume, liquidity, and price chart. No state changes occur—it queries and returns data only.
Attacks that exploit this kind of access
Get detailed information about a token: price, market cap, volume, liquidity, and optionally a price chart. For just the USD price, use get_token_price instead — it. It is categorised as a Read tool in the Relay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Relay MCP Server MCP server in PolicyLayer and add a rule for get_token_details: 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 Relay MCP Server. Nothing to install.
get_token_details 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_token_details 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_token_details. 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_token_details is provided by the Relay MCP Server MCP server (relayprotocol/relay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →