dex_get_pairs_by_address
Get pair information by specific pair address on DexScreener.
This record as markdown: /tools/testinguser1111111-sei-mcp-server/dex-get-pairs-by-address.md
What dex_get_pairs_by_address does on SEI MCP Server V2
AI agents call dex_get_pairs_by_address to retrieve information from SEI MCP Server V2 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why dex_get_pairs_by_address is rated Low
This tool queries and retrieves pair information from DexScreener based on a provided address. It performs a read-only data lookup with no side effects, no code execution, no data modification, and no financial transactions. The verb 'Get' and the lack of any write/execute/destructive operation confirms this is a Read category tool with low severity.
From the tool's definition Tool name 'dex_get_pairs_by_address' and description 'Get pair information by specific pair address on DexScreener' indicate a retrieval operation with no state modification.
Attacks that exploit this kind of access
The rule that runs dex_get_pairs_by_address safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SEI MCP Server V2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dex_get_pairs_by_address, this is the rule to start with:
dex_get_pairs_by_address is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SEI MCP Server V2, apply this rule, and every dex_get_pairs_by_address call is checked against it from then on.
Questions about dex_get_pairs_by_address
Get pair information by specific pair address on DexScreener. 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_pairs_by_address: 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_pairs_by_address 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_pairs_by_address 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_pairs_by_address. 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_pairs_by_address 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.
More on SEI MCP Server V2, and thousands of servers like it.
This server
Across the catalogue