AI agents call get_orders to retrieve information from Alpaca without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and naming convention strongly suggest this tool queries existing order data without side effects. Despite the empty description, the tool name and server context (which includes distinctly action-oriented tools for cancellation, closing, and creation) indicate 'get_orders' is a read-only query operation.
From the tool's definition Tool name 'get_orders' indicates data retrieval with no modification. Context shows sibling tools like 'cancel_order_by_id', 'close_position', and 'create_watchlist' that explicitly perform actions; 'get_orders' follows the retrieval pattern of…
Attacks that exploit this kind of access
get_orders. It is categorised as a Read tool in the Alpaca MCP Server, which means it retrieves data without modifying state.
Register the Alpaca MCP server in PolicyLayer and add a rule for get_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. Nothing to install.
get_orders is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_orders is provided by the Alpaca MCP server (mfoster5303-1/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 →