lifecycle_get_state
Get the current lifecycle state of a session, including available transitions, state history, and SC resolution. Returns current_state, available_transitions, verification_deadline (when state=delivered), timestamps, duration, sc_resolution (the fundamental SC event: resolved, resolved_at, resolv...
This record as markdown: /tools/com-servicialo-mcp-server/lifecycle-get-state.md
What lifecycle_get_state does on Servicialo
AI agents call lifecycle_get_state 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 | |
session_id | string | Yes |
Parameters from the server's own tool schema.
Why lifecycle_get_state is rated Low
This tool retrieves and queries session lifecycle information, state history, and billing resolution details. While it accesses potentially sensitive business data (billing models, resolution information), it performs no write, execute, or destructive operations.
From the tool's definition Tool description uses 'Get the current lifecycle state' and 'Returns' language indicating data retrieval. Retrieves session state, transitions, history, and billing resolution data without modifying it.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs lifecycle_get_state 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_get_state, this is the rule to start with:
lifecycle_get_state 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_get_state call is checked against it from then on.
Questions about lifecycle_get_state
Get the current lifecycle state of a session, including available transitions, state history, and SC resolution. Returns current_state, available_transitions, verification_deadline (when state=delivered), timestamps, duration, sc_resolution (the fundamental SC event: resolved, resolved_at, resolved_by, billing_model), and recent transition history with from/to/at/by/method fields. Requires X-Org-Api-Key. Shape per docs/protocol/sc-event-canonical-schema-2026-04-18.md §7.1. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
lifecycle_get_state accepts 3 parameters: apiKey, orgSlug, session_id. 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_get_state: 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_get_state 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_get_state 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_get_state. 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_get_state 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