get_token
Get detailed information about a specific token on Omni.fun by its contract address. Returns price, market cap, bonding curve progress, holder count, and trading volume.
This record as markdown: /tools/0xzcov-omni-fun-mcp-server/get-token.md
What get_token does on Mcp Omnifun
AI agents call get_token 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_token is rated Low
This is a pure data query tool. It fetches and displays token metadata without creating, modifying, deleting, or executing any side effects. The server's core functionality involves trading and financial operations, but this specific tool only reads token information. No financial transaction, code execution, or data modification occurs.
From the tool's definition Tool retrieves 'detailed information about a specific token' and 'returns price, market cap, bonding curve progress, holder count, and trading volume' — all data retrieval with no modification, deletion, or execution of trades or financial transactions.
Attacks that exploit this kind of access
The rule that runs get_token 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_token, this is the rule to start with:
get_token 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_token call is checked against it from then on.
Questions about get_token
Get detailed information about a specific token on Omni.fun by its contract address. Returns price, market cap, bonding curve progress, holder count, and trading volume. 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_token: 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_token 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_token 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_token. 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_token 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