close_all_positions

Closes all open positions.

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/close-all-positions.md

WHAT IT DOES

What close_all_positions does on Alpaca MCP Server

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

Closing all open positions is a financially destructive and irreversible market action. Once positions are closed at market price, the trades are executed and cannot be undone. Misuse by an AI agent could liquidate an entire portfolio instantly, causing significant financial loss, especially in unfavorable market conditions.

From the tool's definition 'Closes all open positions' - closes ALL open positions simultaneously with no filtering or partial selection

Attacks that exploit this kind of access

RECOMMENDED RULE

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

close_all_positions Hidden

close_all_positions 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": [
    "close_all_positions"
  ]
}

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

FAQ

Questions about close_all_positions

What does the close_all_positions tool do? +

Closes all open positions. 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 close_all_positions? +

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

close_all_positions 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 close_all_positions? +

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

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

close_all_positions 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 → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →