Find markets that match your trading criteria or get detailed market specifications. Use this tool when you need to: - Understand exact tick sizes and minimum order sizes before placing trades - Find all markets for a specific asset (e.g., all BTC-based markets) - Compare contract specifications ...
AI agents call paradex_markets 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 |
|---|---|---|---|
limit | integer | — | Limit the number of results to the specified number. |
offset | integer | — | Offset the results to the specified number. |
market_ids | array | — | Market symbols to get details for. |
jmespath_filter | string | — | JMESPath expression to filter, sort, or limit the results. |
Parameters from the server's own tool schema.
This tool queries market data and specifications without side effects. It enables information retrieval for trading strategy development but does not execute trades, modify accounts, move funds, or change any state. The blast radius of misuse is minimal — an agent could only retrieve market information that is already public.
From the tool's definition Tool name 'paradex_markets' and description indicate it 'retrieves comprehensive details about specified markets' and 'finds markets that match your trading criteria'.
Documented attack patterns abuse exactly the kind of access paradex_markets 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_markets:
{
"version": "1",
"default": "deny",
"tools": {
"paradex_markets": {}
}
}paradex_markets 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.
Find markets that match your trading criteria or get detailed market specifications. Use this tool when you need to: - Understand exact tick sizes and minimum order sizes before placing trades - Find all markets for a specific asset (e.g., all BTC-based markets) - Compare contract specifications across different markets - Identify markets with specific characteristics for your trading strategy Retrieves comprehensive details about specified markets, including base and quote assets, tick size, minimum order size, and other trading parameters. If "ALL" is specified or no market IDs are provided, returns details for all available markets. Example use cases: - Finding the minimum order size for a new trade - Identifying markets with the smallest tick size for precise entries - Checking which assets are available for trading asset_kind is the type of asset in the market. It can be PERP or PERP_OPTION. You can use JMESPath expressions (https://jmespath.org/specification.html) to filter, sort, or limit the results. Use the paradex_filters_model tool to get the filters for a tool. Examples: - Filter by base asset: "[?base_asset=='BTC']" - Sort by 24h volume: "sort_by([*], &volume_24h)" - Limit to top 5 by volume: "[sort_by([*], &to_number(volume_24h))[-5:]]". It is categorised as a Read tool in the Paradex MCP Server MCP Server, which means it retrieves data without modifying state.
paradex_markets accepts 4 parameters: limit, offset, market_ids, jmespath_filter. 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_markets: 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_markets 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_markets 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_markets. 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_markets 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.