AI agents call paradex_orders_history to retrieve information from MCP Paradex Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve historical order records from the Paradex trading platform, which is a read operation with no side effects. While the empty description reduces confidence slightly, the naming pattern and context of related read-only tools (account summary, positions, fills) indicate this is a data retrieval function.
From the tool's definition Tool name 'paradex_orders_history' indicates retrieval of historical order data. Description is empty, limiting certainty.
Documented attack patterns abuse exactly the kind of access paradex_orders_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Paradex Server, and nothing reaches the server without passing your rules. This is the rule we recommend for paradex_orders_history:
{
"version": "1",
"default": "deny",
"tools": {
"paradex_orders_history": {}
}
}paradex_orders_history 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.
paradex_orders_history. It is categorised as a Read tool in the MCP Paradex Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Paradex Server MCP server in PolicyLayer and add a rule for paradex_orders_history: 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 MCP Paradex Server. Nothing to install.
paradex_orders_history 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_orders_history 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_orders_history. 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_orders_history is provided by the MCP Paradex Server MCP server (sv/mcp-paradex-py). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Paradex Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 MCP Paradex Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.