scheduling_reschedule
Reschedule a session to a new time (Servicialo spec). Cancels the original session and creates a new one at the specified datetime. Requires confirm: true and X-Org-Api-Key.
This record as markdown: /tools/com-servicialo-mcp-server/scheduling-reschedule.md
What scheduling_reschedule does on Servicialo
AI agents use scheduling_reschedule to create or update resources in Servicialo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Servicialo environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey | string | — | |
confirm | boolean | Yes | |
orgSlug | string | Yes | |
session_id | string | Yes | |
new_datetime | string | Yes |
Parameters from the server's own tool schema.
Why scheduling_reschedule is rated Medium
This tool both cancels an existing session and creates a new one. While the cancellation aspect could be considered destructive, rescheduling is typically reversible (the session still exists, just at a different time), making Write the most appropriate category.
From the tool's definition Reschedule a session to a new time. Cancels the original session and creates a new one at the specified datetime.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs scheduling_reschedule safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Servicialo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scheduling_reschedule, this is the rule to start with:
scheduling_reschedule 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 Servicialo, apply this rule, and every scheduling_reschedule call is checked against it from then on.
Questions about scheduling_reschedule
Reschedule a session to a new time (Servicialo spec). Cancels the original session and creates a new one at the specified datetime. Requires confirm: true and X-Org-Api-Key. It is categorised as a Write tool in the Servicialo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
scheduling_reschedule accepts 5 parameters: apiKey, confirm, orgSlug, session_id, new_datetime. Required: confirm, orgSlug, session_id, new_datetime. The full parameter table on this page comes from the server's own tool schema.
Register the Servicialo MCP server in PolicyLayer and add a rule for scheduling_reschedule: 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 Servicialo. Nothing to install.
scheduling_reschedule 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 scheduling_reschedule 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 scheduling_reschedule. 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.
scheduling_reschedule is provided by the Servicialo MCP server (@servicialo/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Servicialo, and thousands of servers like it.
This server
Across the catalogue