orbitx__orbitx_dex_chart
HIGH QUALITY DexScreener embed chart for chat. When the user shares a CA/mint and asks for a chart, graph, DexScreener, or candles — call this immediately. Resolves the best liquidity pair and returns markdown with live embed URL, iframe, price/liq/volume stats, interval links, and OrbitX trade l...
This record as markdown: /tools/ai-rokha-rokha/orbitx--orbitx-dex-chart.md
What orbitx__orbitx_dex_chart does on Rokha
AI agents call orbitx__orbitx_dex_chart to retrieve information from Rokha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ca | string | — | Token contract address (mint CA) or DexScreener pair address |
mint | string | — | Alias of ca |
chain | string | — | Chain id (default solana). Examples: solana, ethereum, base, bsc |
theme | string | — | |
iframe | boolean | — | Include HTML iframe block in markdown for clients that render HTML |
authCode | string | — | OrbitX authCode from the dashboard paste message or orbitx_auth_link. After auth, pass this on every tool call (required for Grok). Auth contract: signing tools |
interval | string | — | Chart timeframe for the embed |
Parameters from the server's own tool schema.
Why orbitx__orbitx_dex_chart is rated Low
Fetches and displays chart data without modifying or executing trades.
From the tool's definition Returns markdown with live embed URL, price/liq/volume stats; retrieves chart data
Attacks that exploit this kind of access
The rule that runs orbitx__orbitx_dex_chart safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For orbitx__orbitx_dex_chart, this is the rule to start with:
orbitx__orbitx_dex_chart 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 Rokha, apply this rule, and every orbitx__orbitx_dex_chart call is checked against it from then on.
Questions about orbitx__orbitx_dex_chart
HIGH QUALITY DexScreener embed chart for chat. When the user shares a CA/mint and asks for a chart, graph, DexScreener, or candles — call this immediately. Resolves the best liquidity pair and returns markdown with live embed URL, iframe, price/liq/volume stats, interval links, and OrbitX trade link. Works with Solana mint CA or pair address (also EVM). It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
orbitx__orbitx_dex_chart accepts 7 parameters: ca, mint, chain, theme, iframe, authCode, interval. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for orbitx__orbitx_dex_chart: 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 Rokha. Nothing to install.
orbitx__orbitx_dex_chart 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 orbitx__orbitx_dex_chart 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 orbitx__orbitx_dex_chart. 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.
orbitx__orbitx_dex_chart is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue