cancel_order_by_id

Cancel a specific order by its ID.

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-order-by-id.md

WHAT IT DOES

What cancel_order_by_id does on Alpaca MCP Server

AI agents call cancel_order_by_id 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_order_by_id is rated Critical

Cancelling an order irreversibly terminates a financial instruction in progress. This is a destructive action because once cancelled, the original order ceases to exist and cannot be recovered. In the context of financial trading, this represents a material change to the trader's intended operations with no undo capability.

From the tool's definition Tool name contains 'cancel' which indicates irreversible action; description states 'Cancel a specific order by its ID' - cancelling an active order is an irreversible financial operation that cannot be undone without resubmitting a new order.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cancel_order_by_id 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_order_by_id, this is the rule to start with:

cancel_order_by_id Hidden

cancel_order_by_id 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_order_by_id"
  ]
}

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_order_by_id call is checked against it from then on.

FAQ

Questions about cancel_order_by_id

What does the cancel_order_by_id tool do? +

Cancel a specific order by its ID. 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_order_by_id? +

Register the Alpaca MCP Server MCP server in PolicyLayer and add a rule for cancel_order_by_id: 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_order_by_id? +

cancel_order_by_id 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_order_by_id? +

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

Set action: deny in the PolicyLayer policy for cancel_order_by_id. 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_order_by_id? +

cancel_order_by_id 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_order 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 →