admin_set_availability
Replace the weekly availability schedule for a provider (not additive — overwrites all existing blocks). Get providerId from admin_list_providers first. Schedule uses day names and HH:MM times. Requires X-Org-Api-Key header.
This record as markdown: /tools/com-servicialo-mcp-server/admin-set-availability.md
What admin_set_availability does on Servicialo
AI agents use admin_set_availability 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 | — | |
orgSlug | string | Yes | |
schedule | array | Yes | |
providerId | string | Yes |
Parameters from the server's own tool schema.
Why admin_set_availability is rated Medium
This tool modifies provider availability schedules in a way that overwrites existing configuration. While the operation is technically reversible (another call could restore a previous schedule), the single-call destructive nature of 'overwrites all existing blocks' and the requirement for API key authentication suggest significant business impact.
From the tool's definition 'Replace the weekly availability schedule for a provider (not additive — overwrites all existing blocks)' and 'X-Org-Api-Key header' requirement indicate administrative write access to provider scheduling data.
Risk signalsHandles credentials or secrets (apiKey) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs admin_set_availability 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 admin_set_availability, this is the rule to start with:
admin_set_availability 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 admin_set_availability call is checked against it from then on.
Questions about admin_set_availability
Replace the weekly availability schedule for a provider (not additive — overwrites all existing blocks). Get providerId from admin_list_providers first. Schedule uses day names and HH:MM times. Requires X-Org-Api-Key header. 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.
admin_set_availability accepts 4 parameters: apiKey, orgSlug, schedule, providerId. Required: orgSlug, schedule, providerId. 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 admin_set_availability: 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.
admin_set_availability 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 admin_set_availability 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 admin_set_availability. 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.
admin_set_availability 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