Medium Risk

create_reservation

Create a direct reservation for a SPECIFIC available opening (opening_id required). WHEN TO USE: - Call this AFTER check_availability has returned at least one opening AND the user has chosen which opening_id to book. - Required input includes an opening_id from check_availability. Do NOT call th...

Risk signalsHigh parameter count (15 properties)

Part of the Mcp server.

create_reservation can modify Mcp data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE MCP →

Free to start. No card required.

AI agents use create_reservation to create or modify resources in Mcp. 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 create_reservation 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 Mcp.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_reservation": {
      "limits": [
        {
          "counter": "create_reservation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Mcp policy for all 11 tools.

Get this rule live on your own Mcp server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCP →

View all 11 tools →

These attack patterns abuse exactly the kind of access create_reservation gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so create_reservation only ever does what you allow.

SECURE MCP →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the create_reservation tool do? +

Create a direct reservation for a SPECIFIC available opening (opening_id required). WHEN TO USE: - Call this AFTER check_availability has returned at least one opening AND the user has chosen which opening_id to book. - Required input includes an opening_id from check_availability. Do NOT call this tool without an opening_id. - If check_availability returned no openings, use create_reservation_request instead. REQUIRED FLOW (summary — see resource tableall://flow/direct-reservation for full details): 1. Call get_cancellation_policies and explain cancellation terms (MUST include: "Note: The booking fee is non-refundable regardless of cancellation timing."). 2. Ask the user ONLY for their email first. 3. Call this tool with email only. If response has error USER_NOT_FOUND, collect full name, country, phone, then call again. 4. Show a summary (restaurant, date/time, guests, course, email) and ask explicit confirmation BEFORE calling the tool with the final args. RESPONSE HANDLING: - Store data.access_token (required by get_reservation_status, otherwise 403). - If user.is_new_user is true, MUST display the password_reset_url notice (24-hour validity, also emailed) BEFORE the payment URL. - The payment_url is valid for 30 minutes and is also emailed. SEAT RULES: - Fixed seats: party_size MUST equal fixed_seats. - Flexible seats: party_size MUST be within min_seats and max_seats. For the full step-by-step flow (including exact wording to use with the user), read resource tableall://flow/direct-reservation.. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_reservation? +

Register the MCP server in PolicyLayer and add a rule for create_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 Mcp. Nothing to install.

What risk level is create_reservation? +

create_reservation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_reservation? +

Yes. Add a rate_limit block to the create_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.

How do I block create_reservation completely? +

Set action: deny in the PolicyLayer policy for create_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.

What MCP server provides create_reservation? +

create_reservation is provided by the MCP server (https://mcp.tableall.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp tool call.

Deterministic rules across all 11 Mcp 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.