AI agents call search_pairs 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 the DexScreener API to retrieve pair information matching search criteria. It performs no mutations, deletions, or external operations—purely data retrieval. The blast radius of misuse is minimal (excessive queries or information gathering), placing it squarely in the Read category with low severity.
From the tool's definition Tool name 'search_pairs' and description 'Search for pairs matching query' indicate a query/search operation that retrieves data without modifying state.
Documented attack patterns abuse exactly the kind of access search_pairs 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 search_pairs:
{
"version": "1",
"default": "deny",
"tools": {
"search_pairs": {}
}
}search_pairs 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.
Search for pairs matching query. 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 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 DexScreener MCP Server. Nothing to install.
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 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 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.
search_pairs 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.