bookings_check_availability
List open time slots for a date and party size at the connected booking system, so you can offer real times before creating a booking.
This record as markdown: /tools/com-getmunin-munin/bookings-check-availability.md
What bookings_check_availability does on Munin
AI agents call bookings_check_availability to retrieve information from Munin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why bookings_check_availability is rated Low
Tool queries available slots without modifying, creating, or deleting booking data.
From the tool's definition List open time slots, check availability, retrieves booking information.
Attacks that exploit this kind of access
The rule that runs bookings_check_availability safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bookings_check_availability, this is the rule to start with:
bookings_check_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 Munin, apply this rule, and every bookings_check_availability call is checked against it from then on.
Questions about bookings_check_availability
List open time slots for a date and party size at the connected booking system, so you can offer real times before creating a booking. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.
Register the Munin MCP server in PolicyLayer and add a rule for bookings_check_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 Munin. Nothing to install.
bookings_check_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 bookings_check_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 bookings_check_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.
bookings_check_availability is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Munin, and thousands of servers like it.
This server
Across the catalogue