update_reservation_status

WHAT IT DOES

What update_reservation_status does on Reservation System MCP Server

AI agents use update_reservation_status to create or update resources in Reservation System MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reservation System MCP Server environment.

WHY IT NEEDS A POLICY

Why update_reservation_status needs a policy

This tool modifies appointment records by changing their status (cancellation, recovery, etc.), which is a reversible change operation. It does not delete data (unlike sibling delete_* tools), execute arbitrary code, or involve financial transactions. While it affects business-critical reservation data, the modifications are reversible, placing it in Write category.

From the tool's definition Tool name 'update_reservation_status' and description indicating status updates (取消预约/cancellation, 恢复预约/recovery). The description explicitly states modification operations without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_reservation_status Rate-limited

update_reservation_status 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_reservation_status": {
      "limits": [
        {
          "counter": "update_reservation_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Reservation System MCP Server, so you can run agents against it safely.

FAQ

Questions about update_reservation_status

What does the update_reservation_status tool do? +

更新预约状态（取消预约、恢复预约等）. It is categorised as a Write tool in the Reservation System MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_reservation_status? +

Register the Reservation System MCP Server MCP server in PolicyLayer and add a rule for update_reservation_status: 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 Reservation System MCP Server. Nothing to install.

What risk level is update_reservation_status? +

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

Can I rate-limit update_reservation_status? +

Yes. Add a rate_limit block to the update_reservation_status 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 update_reservation_status completely? +

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

update_reservation_status is provided by the Reservation System MCP Server MCP server (lingki1/mcp-reservation-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.