get_availability
Fetch open booking slots for an event type, grouped by date. event_type_id defaults to the connection
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/get-availability.md
What get_availability does on Max MCP Server
AI agents call get_availability to retrieve information from Max 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_availability is rated Low
The get_availability tool queries and returns booking slot information without side effects. It performs a simple read operation to retrieve availability data. There is no capability to modify, delete, create, or trigger external operations. The low severity reflects minimal risk even if called with unexpected arguments—the worst case is returning incorrect or filtered availability data.
From the tool's definition The tool description uses 'Fetch' and retrieves 'open booking slots' with no mechanism to modify, delete, or execute operations. This is a pure data retrieval operation.
Attacks that exploit this kind of access
The rule that runs get_availability safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_availability, this is the rule to start with:
get_availability 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 Max MCP Server, apply this rule, and every get_availability call is checked against it from then on.
Questions about get_availability
Fetch open booking slots for an event type, grouped by date. event_type_id defaults to the connection. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for get_availability: 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 Max MCP Server. Nothing to install.
get_availability 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_availability 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_availability. 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_availability is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
This server
Across the catalogue