Analyze actual market transactions to understand market sentiment and liquidity. Use this tool when you need to: - Detect large trades that might signal institutional activity - Calculate average trade size during specific periods - Identify buy/sell pressure imbalances - Monitor execution prices...
AI agents call paradex_trades to retrieve information from Paradex MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
market_id | string | — | Market symbol to get trades for. |
end_unix_ms | integer | — | End time in unix milliseconds. |
start_unix_ms | integer | — | Start time in unix milliseconds. |
Parameters from the server's own tool schema.
paradex_trades retrieves and analyzes market transaction data to provide insights into market sentiment and liquidity. This is a passive read operation that queries historical trade information. There are no side effects, data modifications, financial transactions, or code execution involved. The tool is informational only, helping users understand market activity through data analysis.
From the tool's definition Tool description explicitly states 'Analyze actual market transactions' and lists use cases focused on data analysis: 'Detect large trades', 'Calculate average trade size', 'Identify buy/sell pressure', 'Monitor execution prices', 'Understand market momentum'.
Documented attack patterns abuse exactly the kind of access paradex_trades gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Paradex MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for paradex_trades:
{
"version": "1",
"default": "deny",
"tools": {
"paradex_trades": {}
}
}paradex_trades is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Analyze actual market transactions to understand market sentiment and liquidity. Use this tool when you need to: - Detect large trades that might signal institutional activity - Calculate average trade size during specific periods - Identify buy/sell pressure imbalances - Monitor execution prices vs. order book prices - Understand market momentum through trade flow Trade data provides insights into actual market activity versus just orders, helping you understand how other participants are behaving. Example use cases: - Detecting large "whale" transactions that might influence price - Analyzing trade sizes to gauge market participation - Identifying periods of aggressive buying or selling - Understanding trade frequency as an indicator of market interest - Comparing executed prices to orderbook mid-price for market impact analysis. It is categorised as a Read tool in the Paradex MCP Server MCP Server, which means it retrieves data without modifying state.
paradex_trades accepts 3 parameters: market_id, end_unix_ms, start_unix_ms. The full parameter table on this page comes from the server's own tool schema.
Register the Paradex MCP Server MCP server in PolicyLayer and add a rule for paradex_trades: 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 Paradex MCP Server. Nothing to install.
paradex_trades 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 paradex_trades 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 paradex_trades. 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.
paradex_trades is provided by the Paradex MCP Server MCP server (tradeparadex/mcp-paradex-py). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Paradex MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Paradex MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.