Get detailed schema information to build precise data filters. Use this tool when you need to: - Understand exactly what fields are available for filtering - Learn the data types and formats for specific fields - Build complex JMESPath queries with correct syntax - Create sophisticated filtering ...
AI agents call paradex_filters_model 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 |
|---|---|---|---|
tool_name | string | — | The name of the tool to get the filters for. |
Parameters from the server's own tool schema.
This tool only retrieves schema/metadata information about available fields and data types. It has no side effects and does not interact with trading operations, account data, or financial instruments directly. It is purely informational, helping users understand filter structures.
From the tool's definition Get detailed schema information to build precise data filters
Documented attack patterns abuse exactly the kind of access paradex_filters_model 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_filters_model:
{
"version": "1",
"default": "deny",
"tools": {
"paradex_filters_model": {}
}
}paradex_filters_model 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.
Get detailed schema information to build precise data filters. Use this tool when you need to: - Understand exactly what fields are available for filtering - Learn the data types and formats for specific fields - Build complex JMESPath queries with correct syntax - Create sophisticated filtering and sorting expressions Knowing the exact schema helps you construct precise filters that return exactly the data you need, avoiding trial and error. Example use cases: - Learning what fields exist in market data responses - Finding the correct property names for filtering - Understanding data types for numerical comparisons - Building complex multi-criteria filters for large datasets. It is categorised as a Read tool in the Paradex MCP Server MCP Server, which means it retrieves data without modifying state.
paradex_filters_model accepts 1 parameter: tool_name. 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_filters_model: 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_filters_model 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_filters_model 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_filters_model. 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_filters_model 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.