report_no_shows
Report no-show statistics for a period. Group by client, provider, service, or day.
This record as markdown: /tools/com-servicialo-mcp-server/report-no-shows.md
What report_no_shows does on Servicialo
AI agents call report_no_shows 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 |
|---|---|---|---|
limit | integer | — | |
apiKey | string | — | |
dateTo | string | — | |
groupBy | string | — | |
orgSlug | string | Yes | |
dateFrom | string | — |
Parameters from the server's own tool schema.
Why report_no_shows is rated Low
This tool retrieves and aggregates no-show statistics with optional grouping parameters. It performs no creation, modification, deletion, or external execution. The read-only nature is clear from the verb 'report' (retrieve/present) and the absence of any language suggesting data mutation or side effects. The statistics are computed from existing records, making this a straightforward data retrieval operation.
From the tool's definition Tool name 'report_no_shows' and description 'Report no-show statistics for a period. Group by client, provider, service, or day.' indicate data retrieval and aggregation only.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs report_no_shows 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 report_no_shows, this is the rule to start with:
report_no_shows 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 report_no_shows call is checked against it from then on.
Questions about report_no_shows
Report no-show statistics for a period. Group by client, provider, service, or day. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
report_no_shows accepts 6 parameters: limit, apiKey, dateTo, groupBy, orgSlug, dateFrom. Required: orgSlug. 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 report_no_shows: 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.
report_no_shows 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 report_no_shows 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 report_no_shows. 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.
report_no_shows 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