reschedule_meeting
Move a scheduled Cal.com meeting (meeting_id) to new_start (future ISO8601; check get_availability first), with an optional reason. Cal.com emails the attendee the new time. Returns {data: meeting row} with status
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/reschedule-meeting.md
What reschedule_meeting does on Max MCP Server
AI agents call reschedule_meeting to retrieve information from Max MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why reschedule_meeting is rated Low
Even though reschedule_meeting only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs reschedule_meeting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reschedule_meeting, this is the rule to start with:
reschedule_meeting is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every reschedule_meeting call is checked against it from then on.
Questions about reschedule_meeting
Move a scheduled Cal.com meeting (meeting_id) to new_start (future ISO8601; check get_availability first), with an optional reason. Cal.com emails the attendee the new time. Returns {data: meeting row} with status. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for reschedule_meeting: 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 Max MCP Server. Nothing to install.
reschedule_meeting 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 reschedule_meeting 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 reschedule_meeting. 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.
reschedule_meeting is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
This server
Across the catalogue