Reschedule an appointment by ID
AI agents use RescheduleAppointment to create or update resources in MCP Appointment Booking Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Appointment Booking Server environment.
Rescheduling updates an existing appointment record to a new time slot. This is a Write operation (modifying data reversibly), not Destructive since the appointment still exists. Misuse could cause scheduling conflicts or missed appointments, hence medium severity.
From the tool's definition 'Reschedule an appointment by ID' — modifies an existing appointment's time/date, which is a reversible update operation
Attacks that exploit this kind of access
Reschedule an appointment by ID. It is categorised as a Write tool in the MCP Appointment Booking Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Appointment Booking Server MCP server in PolicyLayer and add a rule for RescheduleAppointment: 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 Appointment Booking Server. Nothing to install.
RescheduleAppointment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the RescheduleAppointment 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 RescheduleAppointment. 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.
RescheduleAppointment is provided by the MCP Appointment Booking Server MCP server (manish-awase/mcp-appointment-booking-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →