get_trending_tokens
Get the list of trending/active tokens on Omni.fun. Returns token names, symbols, prices, market caps, and bonding curve progress. Use this to discover what tokens are available for trading.
This record as markdown: /tools/0xzcov-omni-fun-mcp-server/get-trending-tokens.md
What get_trending_tokens does on Mcp Omnifun
AI agents call get_trending_tokens to retrieve information from Mcp Omnifun without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_trending_tokens is rated Low
This tool retrieves and displays data about available tokens without modifying, executing, or transacting anything. It enables discovery of tokens for potential trading but does not itself execute trades, move funds, or change state. The severity is low because misuse (e.g., querying repeatedly) poses minimal risk; it is informational only.
From the tool's definition Tool description states it 'Get[s] the list of trending/active tokens' and 'Returns token names, symbols, prices, market caps, and bonding curve progress.' These are read-only query operations with no side effects.
Attacks that exploit this kind of access
The rule that runs get_trending_tokens safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Omnifun, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_trending_tokens, this is the rule to start with:
get_trending_tokens is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Omnifun, apply this rule, and every get_trending_tokens call is checked against it from then on.
Questions about get_trending_tokens
Get the list of trending/active tokens on Omni.fun. Returns token names, symbols, prices, market caps, and bonding curve progress. Use this to discover what tokens are available for trading. It is categorised as a Read tool in the Mcp Omnifun MCP Server, which means it retrieves data without modifying state.
Register the Mcp Omnifun MCP server in PolicyLayer and add a rule for get_trending_tokens: 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 Mcp Omnifun. Nothing to install.
get_trending_tokens 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_trending_tokens 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_trending_tokens. 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_trending_tokens is provided by the Mcp Omnifun MCP server (0xzcov/omni-fun-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Omnifun, and thousands of servers like it.
This server
Across the catalogue