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

booking_resolve_request

Approve or reject a pending reschedule request (SessionRequest) that a client proposed from the portal — closes the bilateral coordination loop. outcome: "approved" applies the reschedule atomically (moves the session to the proposed slot in the same transaction); "rejected" requires a reason of ...

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/booking-resolve-request.md

What booking_resolve_request does on Servicialo

AI agents use booking_resolve_request 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
outcome string Yes
requestId string Yes

Parameters from the server's own tool schema.

Why booking_resolve_request is rated Medium

This tool modifies session state by rescheduling appointments (moving them to new time slots), which is a reversible write operation. While it affects business logic, it does not delete data (would be Destructive) nor execute arbitrary code (Execute).

From the tool's definition Tool description states it can 'Approve or reject a pending reschedule request' and 'applies the reschedule atomically (moves the session to the proposed slot in the same transaction)'.

Risk signalsHandles credentials or secrets (apiKey)

Questions about booking_resolve_request

What does the booking_resolve_request tool do? +

Approve or reject a pending reschedule request (SessionRequest) that a client proposed from the portal — closes the bilateral coordination loop. outcome: "approved" applies the reschedule atomically (moves the session to the proposed slot in the same transaction); "rejected" requires a reason of at least 10 characters. Idempotent: a request already resolved returns a conflict with its current status. Emits the corresponding session lifecycle events. 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 booking_resolve_request accept? +

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

How do I enforce a policy on booking_resolve_request? +

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

What risk level is booking_resolve_request? +

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

Can I rate-limit booking_resolve_request? +

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

How do I block booking_resolve_request completely? +

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

What MCP server provides booking_resolve_request? +

booking_resolve_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

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