get_orders
AI agents call get_orders to retrieve information from Alpaca MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix universally indicates a query/retrieval operation with no side effects. Despite the empty description, the naming pattern and server context provide high confidence this is a Read operation that queries existing orders. No data is created, modified, deleted, or financial transactions are initiated by merely retrieving order information.
From the tool's definition Tool name 'get_orders' indicates a retrieval operation. The description is empty, but contextual clues from the server (Alpaca Trading API) and sibling tools (cancel_order_by_id, cancel_all_orders are Write/Execute; close_position is Destructive;…
Attacks that exploit this kind of access
get_orders. It is categorised as a Read tool in the Alpaca MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Alpaca MCP Server 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 MCP Server. 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 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 →