Critical Risk →

paradex_cancel_orders

paradex_cancel_orders

How to control paradex_cancel_orders ↓

What paradex_cancel_orders does on MCP Paradex Server

AI agents call paradex_cancel_orders to permanently remove resources in MCP Paradex Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why paradex_cancel_orders needs a policy

Cancelling orders on a trading platform is an irreversible destructive action — once an order is cancelled, it cannot be restored. The name clearly implies bulk cancellation ('orders' plural), which could have significant blast radius if misused by an AI agent, potentially cancelling multiple live trading positions.

From the tool's definition Tool name 'paradex_cancel_orders' on a perpetual futures trading platform server that supports 'placing orders' and 'managing trading accounts'

Documented attack patterns abuse exactly the kind of access paradex_cancel_orders gives an agent:

How to control paradex_cancel_orders

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_cancel_orders:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "paradex_cancel_orders"
  ]
}

paradex_cancel_orders disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register MCP Paradex Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about paradex_cancel_orders

What does the paradex_cancel_orders tool do? +

paradex_cancel_orders. It is categorised as a Destructive tool in the MCP Paradex Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on paradex_cancel_orders? +

Register the MCP Paradex Server MCP server in PolicyLayer and add a rule for paradex_cancel_orders: 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.

What risk level is paradex_cancel_orders? +

paradex_cancel_orders is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit paradex_cancel_orders? +

Yes. Add a rate_limit block to the paradex_cancel_orders 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.

How do I block paradex_cancel_orders completely? +

Set action: deny in the PolicyLayer policy for paradex_cancel_orders. 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.

What MCP server provides paradex_cancel_orders? +

paradex_cancel_orders 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.

Enforce policy on every MCP Paradex Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.