provider_get_stats
Get detailed performance metrics for a provider over a date range: sessions, occupancy, no-show rate, revenue.
This record as markdown: /tools/com-servicialo-mcp-server/provider-get-stats.md
What provider_get_stats does on Servicialo
AI agents call provider_get_stats 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 | — | |
dateTo | string | — | |
orgSlug | string | Yes | |
dateFrom | string | — | |
providerId | string | Yes |
Parameters from the server's own tool schema.
Why provider_get_stats is rated Low
This tool queries and retrieves pre-computed or aggregated performance statistics for reporting/analysis purposes. It has no side effects—it does not create, modify, delete, or trigger external actions. The data is sensitive business intelligence, but the risk category reflects the action performed (retrieval only), not the sensitivity of the data itself.
From the tool's definition Tool description states 'Get detailed performance metrics' — retrieves aggregated statistical data (sessions, occupancy, no-show rate, revenue) with no indication of modification, deletion, or execution of operations.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs provider_get_stats 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 provider_get_stats, this is the rule to start with:
provider_get_stats 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 provider_get_stats call is checked against it from then on.
Questions about provider_get_stats
Get detailed performance metrics for a provider over a date range: sessions, occupancy, no-show rate, revenue. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
provider_get_stats accepts 5 parameters: apiKey, dateTo, orgSlug, dateFrom, 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 provider_get_stats: 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.
provider_get_stats 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 provider_get_stats 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 provider_get_stats. 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.
provider_get_stats 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