portal_cancel_reschedule_request
Cancel a pending reschedule request (SessionRequest) on behalf of the client who proposed it — the client-side withdrawal in the bilateral loop (outcome=cancelled_by_client). Idempotent: a request already cancelled_by_client returns wasAlreadyCancelled=true; a request in another terminal state re...
This record as markdown: /tools/com-servicialo-mcp-server/portal-cancel-reschedule-request.md
What portal_cancel_reschedule_request does on Servicialo
AI agents call portal_cancel_reschedule_request to permanently remove resources in Servicialo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey | string | — | |
orgSlug | string | Yes | |
requestId | string | Yes |
Parameters from the server's own tool schema.
Why portal_cancel_reschedule_request is rated Critical
Cancelling a reschedule request sets it to a terminal state (cancelled_by_client) that cannot be undone — the bilateral negotiation loop is irreversibly terminated from the client side. This is not merely a write/update but a permanent state transition with no reversal path, qualifying as Destructive.
From the tool's definition Cancel a pending reschedule request...client-side withdrawal...outcome=cancelled_by_client. Idempotent: a request already cancelled_by_client returns wasAlreadyCancelled=true; a request in another terminal state returns a conflict.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs portal_cancel_reschedule_request 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 portal_cancel_reschedule_request, this is the rule to start with:
portal_cancel_reschedule_request is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Servicialo, apply this rule, and every portal_cancel_reschedule_request call is checked against it from then on.
Questions about portal_cancel_reschedule_request
Cancel a pending reschedule request (SessionRequest) on behalf of the client who proposed it — the client-side withdrawal in the bilateral loop (outcome=cancelled_by_client). Idempotent: a request already cancelled_by_client returns wasAlreadyCancelled=true; a request in another terminal state returns a conflict. Use booking_list_requests to find pending requests; use booking_resolve_request for the org's own approve/reject. It is categorised as a Destructive tool in the Servicialo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
portal_cancel_reschedule_request accepts 3 parameters: apiKey, orgSlug, requestId. Required: orgSlug, requestId. 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 portal_cancel_reschedule_request: 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.
portal_cancel_reschedule_request is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the portal_cancel_reschedule_request 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 portal_cancel_reschedule_request. 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.
portal_cancel_reschedule_request 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.
Across the catalogue