Get pool data for a specific token from PumpSwap DEX in textual format
AI agents call get_pool_data to retrieve information from Pumpswap 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 pool data from a decentralized exchange (DEX). It performs a read-only operation that fetches information about a liquidity pool for a specified token. There are no side effects, data modifications, financial transactions, or destructive operations involved—it simply returns existing data in textual format.
From the tool's definition Tool name 'get_pool_data' and description 'Get pool data for a specific token from PumpSwap DEX in textual format' indicate retrieval of data without modification.
Documented attack patterns abuse exactly the kind of access get_pool_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pumpswap, and nothing reaches the server without passing your rules. This is the rule we recommend for get_pool_data:
{
"version": "1",
"default": "deny",
"tools": {
"get_pool_data": {}
}
}get_pool_data 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 pool data for a specific token from PumpSwap DEX in textual format. It is categorised as a Read tool in the Pumpswap MCP Server, which means it retrieves data without modifying state.
Register the Pumpswap MCP server in PolicyLayer and add a rule for get_pool_data: 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 Pumpswap. Nothing to install.
get_pool_data 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_pool_data 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_pool_data. 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_pool_data is provided by the Pumpswap MCP server (kukapay/pumpswap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pumpswap, 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.
4 Pumpswap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.