search_tokens
Search for tokens on Omni.fun by name or symbol. Returns matching tokens with their current price and market cap.
This record as markdown: /tools/0xzcov-omni-fun-mcp-server/search-tokens.md
What search_tokens does on Mcp Omnifun
AI agents call search_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 search_tokens is rated Low
This tool queries and retrieves token information (name, symbol, price, market cap) without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with no blast radius if misused by an AI agent—the worst outcome would be retrieving information about tokens.
From the tool's definition Tool description states 'Search for tokens... Returns matching tokens with their current price and market cap.' The verb 'search' and 'returns' indicate data retrieval with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs search_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 search_tokens, this is the rule to start with:
search_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 search_tokens call is checked against it from then on.
Questions about search_tokens
Search for tokens on Omni.fun by name or symbol. Returns matching tokens with their current price and market cap. 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 search_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.
search_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 search_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 search_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.
search_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