update_reservation_time_by_mobile

WHAT IT DOES

What update_reservation_time_by_mobile does on Reservation System MCP Server

AI agents use update_reservation_time_by_mobile 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_time_by_mobile needs a policy

This tool modifies existing reservation records by updating appointment times based on a mobile number. It falls under the Write category as it creates or modifies data reversibly.

From the tool's definition Tool name 'update_reservation_time_by_mobile' and description '根据手机号更改预约时间' (change reservation time by mobile number) indicate modification of existing reservation data. The action is reversible and does not delete or destroy data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_reservation_time_by_mobile Rate-limited

update_reservation_time_by_mobile 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_time_by_mobile": {
      "limits": [
        {
          "counter": "update_reservation_time_by_mobile_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_time_by_mobile

What does the update_reservation_time_by_mobile 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_time_by_mobile? +

Register the Reservation System MCP Server MCP server in PolicyLayer and add a rule for update_reservation_time_by_mobile: 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_time_by_mobile? +

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

Can I rate-limit update_reservation_time_by_mobile? +

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

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

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