cancel_all_orders

Cancel all open orders.

SERVERAlpaca MCP Server SOURCEcliffsgpt/alpaca-mcp-clone

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cliffsgpt-alpaca-mcp-clone/cancel-all-orders.md

WHAT IT DOES

What cancel_all_orders does on Alpaca MCP Server

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

RISK

Why cancel_all_orders is rated Critical

This tool irreversibly cancels all open orders in a trading account, which constitutes a destructive action that cannot be undone. While not permanently deleting data, order cancellation is a one-way financial operation that materially alters account state. The bulk nature ('all orders') and lack of granularity amplifies risk.

From the tool's definition Tool performs 'Cancel all open orders' - a bulk cancellation operation that irreversibly terminates all active trading orders without individual confirmation or recovery mechanism.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cancel_all_orders safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Alpaca MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_all_orders, this is the rule to start with:

cancel_all_orders Hidden

cancel_all_orders is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_all_orders"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Alpaca MCP Server, apply this rule, and every cancel_all_orders call is checked against it from then on.

FAQ

Questions about cancel_all_orders

What does the cancel_all_orders tool do? +

Cancel all open orders. It is categorised as a Destructive tool in the Alpaca MCP 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 cancel_all_orders? +

Register the Alpaca MCP Server MCP server in PolicyLayer and add a rule for cancel_all_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 Alpaca MCP Server. Nothing to install.

What risk level is cancel_all_orders? +

cancel_all_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 cancel_all_orders? +

Yes. Add a rate_limit block to the cancel_all_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 cancel_all_orders completely? +

Set action: deny in the PolicyLayer policy for cancel_all_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 cancel_all_orders? +

cancel_all_orders is provided by the Alpaca MCP Server MCP server (cliffsgpt/alpaca-mcp-clone). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Alpaca MCP Server, and thousands of servers like it.

This server

All 31 Alpaca MCP Server tools → Critical-risk tools on this server →

Across the catalogue

cancel_all_orders on Lighter MCP →sms_cancel_scheduled on Twilio SMS MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →