Get one or multiple pairs by token address (max 30)
AI agents call get_pairs_by_token_addresses to retrieve information from DexScreener MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves pair data from the DexScreener API based on token addresses. It performs no side effects, creates no new data, executes no code, and has no destructive or financial impact. It is a straightforward data retrieval operation with minimal security risk.
From the tool's definition Tool name 'get_pairs_by_token_addresses' and description 'Get one or multiple pairs by token address' indicate data retrieval only. The phrase 'Get' and lack of any modification, deletion, or execution language confirm read-only behavior.
Documented attack patterns abuse exactly the kind of access get_pairs_by_token_addresses gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DexScreener MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_pairs_by_token_addresses:
{
"version": "1",
"default": "deny",
"tools": {
"get_pairs_by_token_addresses": {}
}
}get_pairs_by_token_addresses is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get one or multiple pairs by token address (max 30). It is categorised as a Read tool in the DexScreener MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DexScreener MCP Server MCP server in PolicyLayer and add a rule for get_pairs_by_token_addresses: 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 DexScreener MCP Server. Nothing to install.
get_pairs_by_token_addresses 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_pairs_by_token_addresses 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_pairs_by_token_addresses. 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_pairs_by_token_addresses is provided by the DexScreener MCP Server MCP server (opensvm/dexscreener-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DexScreener MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 DexScreener MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.