Check real-time availability for one or more tours or activities on GuruWalk in a single call. Pass an items array — each entry is independent and has its own type, product_id and date range. Returns a results array where every entry echoes its type and product_id so you can match each response t...
Part of the GuruWalk server.
Free to start. No card required.
AI agents call check_availability to retrieve information from GuruWalk without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though check_availability only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"check_availability": {}
}
}See the full GuruWalk policy for all 4 tools.
These attack patterns abuse exactly the kind of access check_availability gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Check real-time availability for one or more tours or activities on GuruWalk in a single call. Pass an items array — each entry is independent and has its own type, product_id and date range. Returns a results array where every entry echoes its type and product_id so you can match each response to its request. Always batch when checking multiple tours: send them all in one call instead of invoking this tool several times. For paid activities, shows rates by traveler type (adult, child, infant). For free walking tours, no upfront price — travelers pay what they want after the tour. Includes direct booking links. Maximum date range per item: 5 days. Per-item errors (invalid dates, product not found) are reported inside that item's result without failing the rest of the batch. Use this tool when the traveler asks about specific dates, wants to know if something is available, or is ready to book. When the traveler hasn't given specific dates, use the booking date ±2 days as the default search range.. It is categorised as a Read tool in the GuruWalk MCP Server, which means it retrieves data without modifying state.
Register the GuruWalk MCP server in PolicyLayer and add a rule for 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 GuruWalk. Nothing to install.
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 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 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.
check_availability is provided by the GuruWalk MCP server (https://back.guruwalk.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 GuruWalk 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.