tenero_trending_pools

List trending DEX liquidity pools by volume over the last hour.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/tenero-trending-pools.md

WHAT IT DOES

What tenero_trending_pools does on Aibtc

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

RISK

Why tenero_trending_pools is rated Low

This tool queries and returns information about DEX pool trends and volume metrics. It performs no write operations, does not execute trades or financial transactions, and has no destructive or irreversible side effects. It is a pure read/query operation with minimal security risk.

From the tool's definition Tool description states 'List trending DEX liquidity pools by volume over the last hour' — a data retrieval operation with no modification or execution of transactions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tenero_trending_pools safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tenero_trending_pools, this is the rule to start with:

tenero_trending_pools Allowed

tenero_trending_pools is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every tenero_trending_pools call is checked against it from then on.

FAQ

Questions about tenero_trending_pools

What does the tenero_trending_pools tool do? +

List trending DEX liquidity pools by volume over the last hour. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tenero_trending_pools? +

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

What risk level is tenero_trending_pools? +

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

Can I rate-limit tenero_trending_pools? +

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

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

tenero_trending_pools is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →