get_pairs_by_chain_and_address

THE RISK

Low Risk

Why get_pairs_by_chain_and_address needs a policy

This tool purely fetches/queries pair information from DexScreener. It reads market data and has no ability to modify, delete, or transact anything. Misuse potential is minimal as it only returns informational data.

From the tool's definition 'Get one or multiple pairs by chain and pair address' — retrieves DEX pair data by chain and address with no side effects

Documented attack patterns abuse exactly the kind of access get_pairs_by_chain_and_address gives an agent:

POLICY

How to control get_pairs_by_chain_and_address

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_chain_and_address:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_pairs_by_chain_and_address": {}
  }
}

get_pairs_by_chain_and_address is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register DexScreener MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More DexScreener MCP Server tools

Read get_latest_boosted_tokens Get the latest boosted tokens Read get_latest_token_profiles Get the latest token profiles Read get_pairs_by_token_addresses Get one or multiple pairs by token address (max 30) Read get_token_orders Check orders paid for a specific token Read get_top_boosted_tokens Get tokens with most active boosts Read search_pairs Search for pairs matching query

All 7 DexScreener MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_pairs_by_chain_and_address

What does the get_pairs_by_chain_and_address tool do? +

Get one or multiple pairs by chain and pair address. It is categorised as a Read tool in the DexScreener MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pairs_by_chain_and_address? +

Register the DexScreener MCP Server MCP server in PolicyLayer and add a rule for get_pairs_by_chain_and_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 DexScreener MCP Server. Nothing to install.

What risk level is get_pairs_by_chain_and_address? +

get_pairs_by_chain_and_address is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_pairs_by_chain_and_address? +

Yes. Add a rate_limit block to the get_pairs_by_chain_and_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.

How do I block get_pairs_by_chain_and_address completely? +

Set action: deny in the PolicyLayer policy for get_pairs_by_chain_and_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.

What MCP server provides get_pairs_by_chain_and_address? +

get_pairs_by_chain_and_address 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.

Enforce policy on every DexScreener MCP Server tool call.

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.

CHECK YOUR STACK →