AI agents call get_option_snapshot 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.
Despite the empty description, the 'get_' prefix and 'snapshot' term clearly indicate a data retrieval operation that queries option market data without modifying state. However, it is classified as 'high' severity because it runs on a financial trading server (Alpaca) where leaked or misused read access to options data could inform unauthorized trading decisions, market manipulation, or exposure of sensitive…
From the tool's definition Tool name 'get_option_snapshot' indicates data retrieval (snapshot = view/fetch). Server context is financial trading API.
Attacks that exploit this kind of access
get_option_snapshot. 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_option_snapshot: 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_option_snapshot 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_option_snapshot 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_option_snapshot. 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_option_snapshot 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 →