New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

portal_propose_reschedule

Propose a new time for a session on behalf of the client — opens the bilateral coordination loop by creating a pending SessionRequest (it does NOT move the session; the org resolves it with booking_resolve_request). Provide requestedScheduledAt as an ISO datetime (must be future, within ~3 months...

SERVERServicialo SOURCE@servicialo/mcp-server
Medium RISK CLASS
Category Write
Parameters 53 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-servicialo-mcp-server/portal-propose-reschedule.md

What portal_propose_reschedule does on Servicialo

AI agents use portal_propose_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.

ParameterTypeRequiredDescription
apiKey string
reason string
orgSlug string Yes
sessionId string Yes
requestedScheduledAt string Yes

Parameters from the server's own tool schema.

Why portal_propose_reschedule is rated Medium

The tool creates a new pending SessionRequest record — a reversible write operation. It explicitly does not move or modify the session itself, and the actual scheduling change requires a separate resolution step by the org. No data is deleted or irreversibly altered, no code is executed, and no financial transaction occurs.

From the tool's definition creates a pending SessionRequest (it does NOT move the session; the org resolves it with booking_resolve_request)

Risk signalsHandles credentials or secrets (apiKey)

Questions about portal_propose_reschedule

What does the portal_propose_reschedule tool do? +

Propose a new time for a session on behalf of the client — opens the bilateral coordination loop by creating a pending SessionRequest (it does NOT move the session; the org resolves it with booking_resolve_request). Provide requestedScheduledAt as an ISO datetime (must be future, within ~3 months). Gated by the org's session-request flow flag and rate-limited per (client, session). The event records the session's client as the proposer. Use booking_list_requests to track pending requests. 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.

What parameters does portal_propose_reschedule accept? +

portal_propose_reschedule accepts 5 parameters: apiKey, reason, orgSlug, sessionId, requestedScheduledAt. Required: orgSlug, sessionId, requestedScheduledAt. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on portal_propose_reschedule? +

Register the Servicialo MCP server in PolicyLayer and add a rule for portal_propose_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.

What risk level is portal_propose_reschedule? +

portal_propose_reschedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit portal_propose_reschedule? +

Yes. Add a rate_limit block to the portal_propose_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.

How do I block portal_propose_reschedule completely? +

Set action: deny in the PolicyLayer policy for portal_propose_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.

What MCP server provides portal_propose_reschedule? +

portal_propose_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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Servicialo's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.