lifecycle_history
Get the SCEvent stream for a session — all observed transitions reconstructed from status_history. Returns events[] with discriminated union by event_type (sc.scheduled, sc.confirmed, sc.completed, sc.delivered, sc.verified, sc.cancelled, etc.), plus stream_completeness ("complete" | "partial_pre...
This record as markdown: /tools/com-servicialo-mcp-server/lifecycle-history.md
What lifecycle_history does on Servicialo
AI agents call lifecycle_history 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 | — | |
orgSlug | string | Yes | |
session_id | string | Yes | |
event_types | array | — | |
from_sequence | integer | — |
Parameters from the server's own tool schema.
Why lifecycle_history is rated Low
This is a Read operation—it queries and returns historical session transition events. However, severity is elevated to 'medium' rather than 'low' because the stream explicitly contains PII ('delivery_proof' noted in description), creating privacy risk if an agent mishandles the retrieved data.
From the tool's definition Tool retrieves historical event stream data via filters (event_types, from_sequence, limit) with pagination. Description states 'Get the SCEvent stream' and 'Returns events[]' indicating query/retrieval operation with no side effects.
Risk signalsHandles credentials or secrets (apiKey) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs lifecycle_history 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 lifecycle_history, this is the rule to start with:
lifecycle_history 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 lifecycle_history call is checked against it from then on.
Questions about lifecycle_history
Get the SCEvent stream for a session — all observed transitions reconstructed from status_history. Returns events[] with discriminated union by event_type (sc.scheduled, sc.confirmed, sc.completed, sc.delivered, sc.verified, sc.cancelled, etc.), plus stream_completeness ("complete" | "partial_pre_trigger") and pagination cursor. Events carry origin="reprojected_from_status_history" and canonical SCEvent shape per docs/protocol/sc-event-canonical-schema-2026-04-18.md §7.2. Filters: event_types (e.g. ["sc.delivered"]), from_sequence (cursor), limit (default 50, max 500). PII note: delivery_proof clinical fields (summary, outcome, next_steps) are returned only for admin-scoped keys. IMPORTANT: backfilled sc_resolved timestamps do NOT emit sc.resolved events in this stream (Forma B, see decisions log 2026-04-18-lifecycle-history-backfill-policy). For current resolution status, use lifecycle_get_state.sc_resolution. Requires X-Org-Api-Key. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
lifecycle_history accepts 6 parameters: limit, apiKey, orgSlug, session_id, event_types, from_sequence. Required: orgSlug, session_id. 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 lifecycle_history: 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.
lifecycle_history 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 lifecycle_history 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 lifecycle_history. 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.
lifecycle_history 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