Record checkout verification with checklist completion and photo evidence. Used by cleaners or hosts to document property condition.
AI agents use verify_checkout_condition to create or update resources in Vacation Rentals — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vacation Rentals environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
booking_id | string | — | Booking UUID |
photo_urls | array | — | Photo evidence URLs |
property_id | string | — | Property UUID or lilo_code |
verified_by | string | — | Name of person verifying |
issues_found | array | — | List of issues found |
checklist_items | array | — | Completed checklist items |
overall_condition | string | — | Overall condition: excellent, good, fair, poor, damaged |
Parameters from the server's own tool schema.
This tool creates/writes a record of property checkout condition including checklist completion and photo evidence. It is a documentation/write operation with no indication of irreversible deletion or financial transactions. Misuse could result in falsified property condition records, hence medium severity.
From the tool's definition Record checkout verification with checklist completion and photo evidence... document property condition
Risk signalsHigh parameter count (10 properties)
Documented attack patterns abuse exactly the kind of access verify_checkout_condition gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vacation Rentals, and nothing reaches the server without passing your rules. This is the rule we recommend for verify_checkout_condition:
{
"version": "1",
"default": "deny",
"tools": {
"verify_checkout_condition": {
"limits": [
{
"counter": "verify_checkout_condition_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}verify_checkout_condition stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Record checkout verification with checklist completion and photo evidence. Used by cleaners or hosts to document property condition. It is categorised as a Write tool in the Vacation Rentals MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
verify_checkout_condition accepts 7 parameters: booking_id, photo_urls, property_id, verified_by, issues_found, checklist_items, overall_condition. The full parameter table on this page comes from the server's own tool schema.
Register the Vacation Rentals MCP server in PolicyLayer and add a rule for verify_checkout_condition: 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 Vacation Rentals. Nothing to install.
verify_checkout_condition 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 verify_checkout_condition 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 verify_checkout_condition. 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.
verify_checkout_condition is provided by the Vacation Rentals MCP server (lilo-property/vacation-rentals). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vacation Rentals, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
64 Vacation Rentals tools catalogued and risk-classified — across an index of 43,000+ MCP servers.