Retrieves and formats market calendar for specified date range.
AI agents call get_market_calendar 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 fetches read-only market calendar information (trading hours, holidays, etc.) for a specified date range. It has no side effects, does not execute trades, does not modify account state, and does not commit financial obligations. Despite being on a trading-focused server with other high-risk tools, this specific tool is purely informational and poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'get_market_calendar' and description 'Retrieves and formats market calendar for specified date range' indicate a data retrieval operation with no modification, deletion, or financial transaction capability.
Attacks that exploit this kind of access
Retrieves and formats market calendar for specified date range. 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_market_calendar: 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_market_calendar 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_market_calendar 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_market_calendar. 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_market_calendar 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 →