Fetch comprehensive token details including price, market data, and trading metrics from DexScreener API
AI agents call getTokenDetails to retrieve information from HyperEVM MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available information about tokens without modifying any state, executing code, or triggering financial operations. It is a simple read operation to query token metadata and pricing information. Even in the context of a DeFi protocol, fetching token details is a fundamental read operation used for decision-making, not for executing transactions or transfers.
From the tool's definition Tool name 'getTokenDetails' and description 'Fetch comprehensive token details including price, market data, and trading metrics' indicate a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch comprehensive token details including price, market data, and trading metrics from DexScreener API. It is categorised as a Read tool in the HyperEVM MCP MCP Server, which means it retrieves data without modifying state.
Register the HyperEVM MCP server in PolicyLayer and add a rule for getTokenDetails: 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 HyperEVM MCP. Nothing to install.
getTokenDetails 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 getTokenDetails 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 getTokenDetails. 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.
getTokenDetails is provided by the HyperEVM MCP server (playainetwork/hyperevm-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 →