Push a trading signal to the Pionex signal platform (signal provider use). The platform forwards the signal to all smart copy bots subscribed to the given signalType. Use action='buy' to open a position and action='sell' to close it. Endpoint: POST /api/v1/bot/signal/listener
AI agents use pionex_bot_signal_listener to commit financial operations through Pionex Trade — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
base | string | Yes | Base currency (e.g. BTC). |
data | object | Yes | |
time | string | Yes | Signal timestamp in RFC 3339 format (e.g. '2024-01-01T12:00:00Z'). |
price | string | Yes | Current price at time of signal (e.g. '85000'). |
quote | string | Yes | Quote currency (e.g. USDT). |
signalType | string | Yes | Signal provider UUID. |
signalParam | string | Yes | Signal parameters as a JSON string (use '{}' for no extra params). |
Parameters from the server's own tool schema.
This tool directly triggers financial trades across all subscribed smart copy bots simultaneously. A single misuse could open or close positions for many users, causing potentially large and irreversible financial losses. It operates on a trading platform and directly controls buy/sell actions, making it Financial category with critical severity due to the broad blast radius (all subscribed bots affected).
From the tool's definition Push a trading signal to the Pionex signal platform... forwards the signal to all smart copy bots subscribed... action='buy' to open a position and action='sell' to close it
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
Push a trading signal to the Pionex signal platform (signal provider use). The platform forwards the signal to all smart copy bots subscribed to the given signalType. Use action='buy' to open a position and action='sell' to close it. Endpoint: POST /api/v1/bot/signal/listener. It is categorised as a Financial tool in the Pionex Trade MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
pionex_bot_signal_listener accepts 7 parameters: base, data, time, price, quote, signalType, signalParam. Required: base, data, time, price, quote, signalType, signalParam. 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_bot_signal_listener: 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_bot_signal_listener is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pionex_bot_signal_listener 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_bot_signal_listener. 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_bot_signal_listener 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 →