delivery_confirmations_list
List the delivery-confirmation ledger for an organization's sessions. Each row reflects the DeliveryProof overlay: whether the provider confirmed delivery, whether the client confirmed, and whether the system auto-confirmed after the verification window (silence). Filter by state — awaiting_clien...
This record as markdown: /tools/com-servicialo-mcp-server/delivery-confirmations-list.md
What delivery_confirmations_list does on Servicialo
AI agents call delivery_confirmations_list 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 |
|---|---|---|---|
page | integer | — | |
limit | integer | — | |
state | string | — | |
apiKey | string | — | |
orgSlug | string | Yes | |
sessionId | string | — |
Parameters from the server's own tool schema.
Why delivery_confirmations_list is rated Low
The tool queries and lists delivery confirmation data with optional filtering. It returns read-only fields (confirmation flags, timestamps, hasEvidence boolean) without side effects. This is a standard data retrieval operation.
From the tool's definition 'List the delivery-confirmation ledger' — retrieves confirmation status records without modifying them. Supports filtering and lookup but no create/update/delete operations.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs delivery_confirmations_list 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 delivery_confirmations_list, this is the rule to start with:
delivery_confirmations_list 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 delivery_confirmations_list call is checked against it from then on.
Questions about delivery_confirmations_list
List the delivery-confirmation ledger for an organization's sessions. Each row reflects the DeliveryProof overlay: whether the provider confirmed delivery, whether the client confirmed, and whether the system auto-confirmed after the verification window (silence). Filter by state — awaiting_client (provider confirmed, client has not, not yet auto-confirmed), confirmed (client confirmed or auto-confirmed), or provider_pending (proof exists but the provider has not confirmed delivery) — or look one up by sessionId. Privacy: returns confirmation flags/timestamps and a hasEvidence boolean only, never the evidence summary content. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
delivery_confirmations_list accepts 6 parameters: page, limit, state, apiKey, orgSlug, sessionId. 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 delivery_confirmations_list: 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.
delivery_confirmations_list 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 delivery_confirmations_list 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 delivery_confirmations_list. 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.
delivery_confirmations_list 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