check_availability_and_list_bookings

check_availability_and_list_bookings

Server DiSH MCP Server samgwd/dish-mcp
Category Read
Risk class Low
Parameters 00 required

What check_availability_and_list_bookings does on DiSH MCP Server

AI agents call check_availability_and_list_bookings to retrieve information from DiSH MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_availability_and_list_bookings needs a policy

The tool performs only data retrieval—checking room availability and listing existing bookings. These are read-only operations with no side effects, no data modification, and no irreversible actions. The sibling tools 'book_room' (Write) and 'cancel_booking' (Destructive) are clearly more severe. Low severity because misuse of a read operation causes no harm to system state.

From the tool's definition Tool name 'check_availability_and_list_bookings' indicates retrieval operations: 'check_availability' and 'list_bookings' are query/read operations with no modification. Server description confirms it 'search[es] availability' as a core function.

Questions about check_availability_and_list_bookings

What does the check_availability_and_list_bookings tool do? +

check_availability_and_list_bookings. It is categorised as a Read tool in the DiSH MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_availability_and_list_bookings? +

Register the DiSH MCP Server MCP server in PolicyLayer and add a rule for check_availability_and_list_bookings: 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 DiSH MCP Server. Nothing to install.

What risk level is check_availability_and_list_bookings? +

check_availability_and_list_bookings is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_availability_and_list_bookings? +

Yes. Add a rate_limit block to the check_availability_and_list_bookings 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.

How do I block check_availability_and_list_bookings completely? +

Set action: deny in the PolicyLayer policy for check_availability_and_list_bookings. 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.

What MCP server provides check_availability_and_list_bookings? +

check_availability_and_list_bookings is provided by the DiSH MCP Server MCP server (samgwd/dish-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.