# get_how_to_buy

Get step-by-step instructions for buying a token on Omni.fun, including which contracts to interact with on each chain.

Agent View of the PolicyLayer registry record for `get_how_to_buy`. HTML page: https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/get-how-to-buy

## Facts

- Tool: `get_how_to_buy`
- Server: Mcp Omnifun (`0xzcov/omni-fun-mcp-server`) — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server.md
- Homepage: https://github.com/0xzcov/omni-fun-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_how_to_buy",
    "arguments": {}
  }
}
```

## Why get_how_to_buy is rated Low

This tool retrieves instructional information about how to purchase tokens but does not itself execute trades, move funds, or modify data. It is purely informational (Read category). Severity is low because misuse would only result in the agent following incorrect purchasing steps, not irreversible financial loss or unauthorized transactions.

From the tool's own definition: "Tool returns 'step-by-step instructions' and 'contracts to interact with' — informational guidance only. The description contains no verbs indicating state changes, fund movement, or code execution. It retrieves and displays data."

## Use case

AI agents call get_how_to_buy 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Omnifun:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_how_to_buy": {}
  }
}
```

## Other tools on Mcp Omnifun (7)

- `simulate_trade` — Execute — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/simulate-trade.md
- `get_agent` — Read — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/get-agent.md
- `get_bonding_curve` — Read — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/get-bonding-curve.md
- `get_supported_chains` — Read — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/get-supported-chains.md
- `get_token` — Read — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/get-token.md
- `get_trending_tokens` — Read — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/get-trending-tokens.md
- `search_tokens` — Read — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/search-tokens.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xzcov-omni-fun-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xzcov-omni-fun-mcp-server