get_crypto_bars
AI agents call get_crypto_bars 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 retrieves historical or current cryptocurrency OHLC (open, high, low, close) bar data for analysis. It performs no trading operations, does not modify positions or orders, and has no destructive or financial consequences. Classification as Read with low severity is appropriate.
From the tool's definition Tool name 'get_crypto_bars' indicates retrieval of cryptocurrency price/volume data (bars). The Alpaca API pattern for 'get_*' endpoints is read-only data retrieval with no side effects.
Attacks that exploit this kind of access
get_crypto_bars. 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_crypto_bars: 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_crypto_bars 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_crypto_bars 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_crypto_bars. 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_crypto_bars 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 →