Prepare a one-tap booking handoff for the user's chosen campground/dates. Returns a pre-filled deep link to the operator's reservation page plus the booking-window context (release date/time, ToS-compliant guidance, alert suggestion) the agent needs to advise the user. Does NOT book on behalf — t...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Outdoorithm server.
Free to start. No card required.
AI agents call prepare_reservation to retrieve information from Outdoorithm 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 prepare_reservation 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": {
"prepare_reservation": {}
}
}See the full Outdoorithm policy for all 18 tools.
These attack patterns abuse exactly the kind of access prepare_reservation 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.
Prepare a one-tap booking handoff for the user's chosen campground/dates. Returns a pre-filled deep link to the operator's reservation page plus the booking-window context (release date/time, ToS-compliant guidance, alert suggestion) the agent needs to advise the user. Does NOT book on behalf — third-party booking is prohibited by Recreation.gov, ReserveCalifornia, ReserveAmerica, and every other supported public-land operator. Pair with check_availability first to confirm the dates are reservable and to surface site-specific booking_url values when available. Args: campground_id: Outdoorithm CUID (e.g. RecreationDotGov:232447). start_date: Check-in date (YYYY-MM-DD). end_date: Check-out date (YYYY-MM-DD). party_size: Optional group size. Surfaced in the user-facing summary; most operators don't accept this in URL params, so it isn't embedded in the deep link.. It is categorised as a Read tool in the Outdoorithm MCP Server, which means it retrieves data without modifying state.
Register the Outdoorithm MCP server in PolicyLayer and add a rule for prepare_reservation: 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 Outdoorithm. Nothing to install.
prepare_reservation 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 prepare_reservation 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 prepare_reservation. 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.
prepare_reservation is provided by the Outdoorithm MCP server (https://mcp.outdoorithm.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 18 Outdoorithm 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.