get_market_calendar
Retrieves and formats market calendar for specified date range.
This record as markdown: /tools/cliffsgpt-alpaca-mcp-clone/get-market-calendar.md
What get_market_calendar does on Alpaca MCP Server
AI agents call get_market_calendar to retrieve information from Alpaca MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_market_calendar is rated Low
This tool merely queries and retrieves market calendar information (trading hours, holidays, etc.) for a given date range. It has no side effects, does not execute trades or code, does not modify any state, and does not involve financial transactions. It is purely informational data access, placing it squarely in the Read category with low severity.
From the tool's definition Tool name 'get_market_calendar' and description 'Retrieves and formats market calendar for specified date range' indicate data retrieval with no modification, creation, execution, or deletion of resources.
Attacks that exploit this kind of access
The rule that runs get_market_calendar safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Alpaca MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_market_calendar, this is the rule to start with:
get_market_calendar is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Alpaca MCP Server, apply this rule, and every get_market_calendar call is checked against it from then on.
Questions about get_market_calendar
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 (cliffsgpt/alpaca-mcp-clone). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Alpaca MCP Server, and thousands of servers like it.
This server
Across the catalogue