Create a fallback non-VRP booking and return a host-configured Stripe checkout URL. Use only after explicit user confirmation when no signed VRP direct_booking_url is available. When get_verified_stay_offer returns a signed direct_booking_url, route the guest to that host-domain URL instead and d...
Risk signalsHigh parameter count (10 properties)
Part of the Hemmabo server.
Free to start. No card required.
AI agents use hemmabo_booking_checkout to create or modify resources in Hemmabo. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call hemmabo_booking_checkout repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Hemmabo.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"hemmabo_booking_checkout": {
"limits": [
{
"counter": "hemmabo_booking_checkout_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Hemmabo policy for all 15 tools.
These attack patterns abuse exactly the kind of access hemmabo_booking_checkout gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Create a fallback non-VRP booking and return a host-configured Stripe checkout URL. Use only after explicit user confirmation when no signed VRP direct_booking_url is available. When get_verified_stay_offer returns a signed direct_booking_url, route the guest to that host-domain URL instead and do not collect guest contact details in chat. Do NOT use for search, browsing, availability, verified-offer display, demo proof, or direct host-domain link presentation. Do NOT call twice for the same booking - check hemmabo_booking_status first to avoid duplicate charges. Returns reservationId, paymentUrl, and pricing details.. It is categorised as a Write tool in the Hemmabo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hemmabo MCP server in PolicyLayer and add a rule for hemmabo_booking_checkout: 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 Hemmabo. Nothing to install.
hemmabo_booking_checkout is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the hemmabo_booking_checkout 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 hemmabo_booking_checkout. 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.
hemmabo_booking_checkout is provided by the Hemmabo MCP server (HemmaBo-se/hemmabo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Hemmabo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.