Search for token pairs on DexScreener by token name, symbol, or address.
AI agents call dex_search_pairs 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.
The tool performs a read-only search/query operation against DexScreener data. It takes search parameters (token name, symbol, or address) and returns matching token pair information. There are no side effects, no state modifications, no financial transactions, and no code execution.
From the tool's definition Tool name contains 'search' and description states 'Search for token pairs on DexScreener by token name, symbol, or address.' This is a query operation that retrieves data without modifying state or triggering transactions.
Attacks that exploit this kind of access
Search for token pairs on DexScreener by token name, symbol, or address. 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_search_pairs: 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_search_pairs 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_search_pairs 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_search_pairs. 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_search_pairs 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 →