New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

coingecko_getPoolsByToken

Get all liquidity pools for a token from CoinGecko on-chain DEX tracker. SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and e...

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp
Low RISK CLASS
Category Read
Parameters 31 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/coingecko-getpoolsbytoken.md

What coingecko_getPoolsByToken does on Sap

AI agents call coingecko_getPoolsByToken to retrieve information from Sap without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
page number Page pagination control for Coingecko Get Pools By Token.
network string Network Solana network or cluster selector for Coingecko Get Pools By Token.
tokenAddress string Yes Token contract/mint address

Parameters from the server's own tool schema.

Why coingecko_getPoolsByToken is rated Low

Tool retrieves off-chain market data without modifying state or executing external operations.

From the tool's definition Get all liquidity pools for a token from CoinGecko; operation class read; market data

Questions about coingecko_getPoolsByToken

What does the coingecko_getPoolsByToken tool do? +

Get all liquidity pools for a token from CoinGecko on-chain DEX tracker. SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and escrow state remain authoritative for payments. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. It is categorised as a Read tool in the Sap MCP Server, which means it retrieves data without modifying state.

What parameters does coingecko_getPoolsByToken accept? +

coingecko_getPoolsByToken accepts 3 parameters: page, network, tokenAddress. Required: tokenAddress. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on coingecko_getPoolsByToken? +

Register the Sap MCP server in PolicyLayer and add a rule for coingecko_getPoolsByToken: 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 Sap. Nothing to install.

What risk level is coingecko_getPoolsByToken? +

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

Can I rate-limit coingecko_getPoolsByToken? +

Yes. Add a rate_limit block to the coingecko_getPoolsByToken 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 coingecko_getPoolsByToken completely? +

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

coingecko_getPoolsByToken is provided by the Sap MCP server (https://mcp.sap.oobeprotocol.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Sap, and thousands of servers like it.

This server

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sap's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.