Get token pair data across multiple chains for the same token contract addresses.
AI agents call dex_get_multi_chain_token_data to retrieve information from SEI MCP Server V2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries token pair data without side effects. It performs a read-only operation on blockchain data, analogous to a database SELECT query. There is no creation, modification, deletion, code execution, or financial transaction involved. The low severity reflects minimal risk of misuse—retrieving public blockchain data poses no immediate harm even if an AI agent calls it unexpectedly.
From the tool's definition Tool name includes 'get' and description states 'Get token pair data' with no mention of state modification, deletion, or execution. The operation is purely data retrieval across blockchain chains.
Attacks that exploit this kind of access
Get token pair data across multiple chains for the same token contract addresses. It is categorised as a Read tool in the SEI MCP Server V2 MCP Server, which means it retrieves data without modifying state.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for dex_get_multi_chain_token_data: 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 SEI MCP Server V2. Nothing to install.
dex_get_multi_chain_token_data 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 dex_get_multi_chain_token_data 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 dex_get_multi_chain_token_data. 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.
dex_get_multi_chain_token_data is provided by the SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). 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 →