availability_get_provider_schedule
Get the configured weekly availability schedule for a provider (not free slots, but the base configuration). Use admin_set_availability to modify.
This record as markdown: /tools/com-servicialo-mcp-server/availability-get-provider-schedule.md
What availability_get_provider_schedule does on Servicialo
AI agents call availability_get_provider_schedule 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey | string | — | |
orgSlug | string | Yes | |
providerId | string | Yes |
Parameters from the server's own tool schema.
Why availability_get_provider_schedule is rated Low
This tool queries and retrieves data (a provider's availability schedule configuration) without creating, modifying, deleting, or executing operations. It is explicitly read-only ('not free slots, but the base configuration'), with instructions to use admin_set_availability for any modifications. No destructive, financial, or executable actions are performed.
From the tool's definition Tool description: 'Get the configured weekly availability schedule for a provider' — retrieves provider schedule configuration without modification or side effects.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs availability_get_provider_schedule 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 availability_get_provider_schedule, this is the rule to start with:
availability_get_provider_schedule is read-only, so it stays allowed. 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 availability_get_provider_schedule call is checked against it from then on.
Questions about availability_get_provider_schedule
Get the configured weekly availability schedule for a provider (not free slots, but the base configuration). Use admin_set_availability to modify. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
availability_get_provider_schedule accepts 3 parameters: apiKey, orgSlug, providerId. Required: orgSlug, 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 availability_get_provider_schedule: 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.
availability_get_provider_schedule is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the availability_get_provider_schedule 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 availability_get_provider_schedule. 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.
availability_get_provider_schedule 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