reschedule_booking
Commit the exact owner-confirmed reschedule preview using both independent scheduling grants. This can notify the recipient, including cancellation. Reuse the same preview, hash and confirmation reference after uncertainty. Missing private process custody permits receipt recovery but cannot autho...
This record as markdown: /tools/com-meta-council-decision-intelligence/reschedule-booking.md
What reschedule_booking does on Meta Council
AI agents use reschedule_booking to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
preview_id | string | Yes | |
preview_hash | string | Yes | |
confirmation_id | string | Yes |
Parameters from the server's own tool schema.
Why reschedule_booking is rated Medium
An AI agent can call reschedule_booking faster than any human can review: one bad instruction and it creates or modifies resources in Meta Council by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs reschedule_booking safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reschedule_booking, this is the rule to start with:
reschedule_booking 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every reschedule_booking call is checked against it from then on.
Questions about reschedule_booking
Commit the exact owner-confirmed reschedule preview using both independent scheduling grants. This can notify the recipient, including cancellation. Reuse the same preview, hash and confirmation reference after uncertainty. Missing private process custody permits receipt recovery but cannot authorize a new dispatch; no manage secret is reconstructed. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
reschedule_booking accepts 3 parameters: preview_id, preview_hash, confirmation_id. Required: preview_id, preview_hash, confirmation_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for reschedule_booking: 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 Meta Council. Nothing to install.
reschedule_booking 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 reschedule_booking 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_booking. 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_booking is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue