High Risk →

geckoterminal_new_pools

Get newly created pools across all networks or on a specific network - catch new token launches early

How to control geckoterminal_new_pools ↓

AI agents invoke geckoterminal_new_pools to trigger actions in BNB Chain MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

geckoterminal_new_pools triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for geckoterminal_new_pools:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "geckoterminal_new_pools": {
      "limits": [
        {
          "counter": "geckoterminal_new_pools_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

geckoterminal_new_pools stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register BNB Chain MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the geckoterminal_new_pools tool do? +

Get newly created pools across all networks or on a specific network - catch new token launches early. It is categorised as a Execute tool in the BNB Chain MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on geckoterminal_new_pools? +

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

What risk level is geckoterminal_new_pools? +

geckoterminal_new_pools is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit geckoterminal_new_pools? +

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

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

geckoterminal_new_pools is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BNB Chain MCP tool call.

Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.