alpaca-deleteWatchlist
AI agents call alpaca-deleteWatchlist to permanently remove resources in Alpaca API MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call alpaca-deleteWatchlist doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Alpaca API MCP Server is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
alpaca-deleteWatchlist. It is categorised as a Destructive tool in the Alpaca API MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Alpaca API MCP Server MCP server in PolicyLayer and add a rule for alpaca-deleteWatchlist: 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 API MCP Server. Nothing to install.
alpaca-deleteWatchlist is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the alpaca-deleteWatchlist 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 alpaca-deleteWatchlist. 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.
alpaca-deleteWatchlist is provided by the Alpaca API MCP Server MCP server (wlu03/alpaca-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.