get_stock_trades
AI agents call get_stock_trades 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.
This tool appears to query or retrieve stock trade information—a read operation with no side effects. While the empty description reduces confidence slightly, the naming convention, the 'get_' prefix pattern consistent with other read tools on the server, and the lack of any modification verbs (create, update, delete, cancel, close) indicate this is a data retrieval function.
From the tool's definition Tool name 'get_stock_trades' indicates a retrieval operation. The description is empty, but the verb 'get' and context within an Alpaca trading server (which provides 'get_account_info', 'get_all_assets', 'get_asset_info' as read-only queries) strongly…
Attacks that exploit this kind of access
get_stock_trades. 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_stock_trades: 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_stock_trades 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_stock_trades 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_stock_trades. 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_stock_trades is provided by the Alpaca MCP Server MCP server (jbkix06/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 →