Verify the exchange is fully operational before executing trades. Use this tool when you need to: - Check if Paradex is functioning normally before placing important orders - Verify system status if you encounter unexpected behavior - Confirm that maintenance periods are not in effect - Check exc...
AI agents call paradex_system_state 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.
This tool retrieves system status and operational state information for informational purposes only. It has no side effects, does not execute trades, does not modify any data, and does not commit financial obligations. It is purely a monitoring/diagnostic tool used to validate preconditions before other operations.
From the tool's definition Tool description indicates it 'Verify[ies] the exchange is fully operational' and 'Check[s] if Paradex is functioning normally' and 'Verify[ies] system status' and 'Check[s] exchange clock synchronization'.
Documented attack patterns abuse exactly the kind of access paradex_system_state 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_system_state:
{
"version": "1",
"default": "deny",
"tools": {
"paradex_system_state": {}
}
}paradex_system_state 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.
Verify the exchange is fully operational before executing trades. Use this tool when you need to: - Check if Paradex is functioning normally before placing important orders - Verify system status if you encounter unexpected behavior - Confirm that maintenance periods are not in effect - Check exchange clock synchronization with your own systems This is especially important before executing critical trades or when experiencing unexpected behavior from other API calls. Example use cases: - Verifying the exchange is operational before executing a trading strategy - Checking if maintenance mode is active when experiencing delays - Confirming exchange status during periods of market volatility - Diagnosing API issues by checking system health. It is categorised as a Read tool in the Paradex MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Paradex MCP Server MCP server in PolicyLayer and add a rule for paradex_system_state: 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_system_state 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_system_state 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_system_state. 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_system_state 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.