Get 24-hour ticker(s): open, close, high, low, volume, amount, count. Optional symbol or type (SPOT/PERP).
AI agents call pionex_market_get_tickers to retrieve information from Pionex Trade without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | If symbol is not specified, filter by type. |
symbol | string | — | e.g. BTC_USDT; if omitted, returns all tickers filtered by type |
Parameters from the server's own tool schema.
This tool retrieves market ticker data without modifying any state. It performs a straightforward query operation to fetch public market information. The severity is low because ticker data is publicly available and retrieving it poses no security or operational risk to the user's account or funds.
From the tool's definition Tool name contains 'get_tickers' and description states 'Get 24-hour ticker(s)' with only read-only data fields (open, close, high, low, volume, amount, count). No side effects or mutations described.
Attacks that exploit this kind of access
Get 24-hour ticker(s): open, close, high, low, volume, amount, count. Optional symbol or type (SPOT/PERP). It is categorised as a Read tool in the Pionex Trade MCP Server, which means it retrieves data without modifying state.
pionex_market_get_tickers accepts 2 parameters: type, symbol. The full parameter table on this page comes from the server's own tool schema.
Register the Pionex Trade MCP server in PolicyLayer and add a rule for pionex_market_get_tickers: 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 Pionex Trade. Nothing to install.
pionex_market_get_tickers 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 pionex_market_get_tickers 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 pionex_market_get_tickers. 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.
pionex_market_get_tickers is provided by the Pionex Trade MCP server (@pionex/pionex-trade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →