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

booking_list_requests

List the reschedule requests (SessionRequest) of an organization — the org side of the bilateral coordination loop a client opens from the portal. Filter by status (pending|all|resolved, default pending), sessionId or clientId. Returns the proposed slot, current session state, and who proposed it...

SERVERServicialo SOURCE@servicialo/mcp-server
Low RISK CLASS
Category Read
Parameters 81 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-servicialo-mcp-server/booking-list-requests.md

What booking_list_requests does on Servicialo

AI agents call booking_list_requests to retrieve information from Servicialo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
limit integer
apiKey string
cursor string
status string
orgSlug string Yes
clientId string
sessionId string
includePendingCount boolean

Parameters from the server's own tool schema.

Why booking_list_requests is rated Low

This is a read-only query operation that retrieves and lists existing booking request data. It filters and paginates results but performs no modifications, deletions, or external operations. The explicit 'Read-only' declaration and reference to a separate tool (booking_resolve_request) for modifications confirm this is purely a data retrieval function with minimal blast radius if misused.

From the tool's definition Tool description explicitly states 'Read-only' and 'List the reschedule requests' with filtering capabilities.

Risk signalsHandles credentials or secrets (apiKey)

Questions about booking_list_requests

What does the booking_list_requests tool do? +

List the reschedule requests (SessionRequest) of an organization — the org side of the bilateral coordination loop a client opens from the portal. Filter by status (pending|all|resolved, default pending), sessionId or clientId. Returns the proposed slot, current session state, and who proposed it. Cursor-paginated. Set includePendingCount: true to also get the count of pending requests (powers the sidebar badge). Read-only. Use booking_resolve_request to approve or reject one. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.

What parameters does booking_list_requests accept? +

booking_list_requests accepts 8 parameters: limit, apiKey, cursor, status, orgSlug, clientId, sessionId, includePendingCount. Required: orgSlug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on booking_list_requests? +

Register the Servicialo MCP server in PolicyLayer and add a rule for booking_list_requests: 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_list_requests? +

booking_list_requests is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit booking_list_requests? +

Yes. Add a rate_limit block to the booking_list_requests 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_list_requests completely? +

Set action: deny in the PolicyLayer policy for booking_list_requests. 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_list_requests? +

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

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