place_crypto_order
AI agents use place_crypto_order to commit financial operations through Alpaca MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Despite the empty description, the tool name clearly indicates placing a cryptocurrency order. Given the server context (Alpaca Trading API, crypto trading support), this tool almost certainly executes a financial transaction to buy or sell crypto assets. Sibling tools like 'close_position' and 'exercise_options_position' confirm this is a live trading environment.
From the tool's definition Tool name 'place_crypto_order' on a server explicitly described as supporting 'stock, options, and crypto trading' — placing an order commits a financial transaction.
Attacks that exploit this kind of access
place_crypto_order. It is categorised as a Financial tool in the Alpaca MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Alpaca MCP Server MCP server in PolicyLayer and add a rule for place_crypto_order: 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.
place_crypto_order is a Financial 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 place_crypto_order 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 place_crypto_order. 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.
place_crypto_order is provided by the Alpaca MCP Server MCP server (metachain-org/alpaca-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →