bookings_cancel_my_booking
Cancel one of the calling end-user’s own bookings by
This record as markdown: /tools/com-getmunin-munin/bookings-cancel-my-booking.md
What bookings_cancel_my_booking does on Munin
AI agents call bookings_cancel_my_booking to permanently remove resources in Munin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why bookings_cancel_my_booking is rated Critical
Cancelling a booking is irreversible and removes a confirmed reservation permanently.
From the tool's definition Cancel one of the calling end-user's own bookings
Attacks that exploit this kind of access
The rule that runs bookings_cancel_my_booking 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_cancel_my_booking, this is the rule to start with:
bookings_cancel_my_booking is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every bookings_cancel_my_booking call is checked against it from then on.
Questions about bookings_cancel_my_booking
Cancel one of the calling end-user’s own bookings by. It is categorised as a Destructive tool in the Munin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Munin MCP server in PolicyLayer and add a rule for bookings_cancel_my_booking: 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_cancel_my_booking is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bookings_cancel_my_booking 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_cancel_my_booking. 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_cancel_my_booking 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.
Across the catalogue