snow_hr_lifecycle_event

SERVERSerac SOURCEserac-labs/serac

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/serac/snow-hr-lifecycle-event.md

WHAT IT DOES

What snow_hr_lifecycle_event does on Serac

AI agents use snow_hr_lifecycle_event to create or update resources in Serac, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.

RISK

Why snow_hr_lifecycle_event is rated Medium

This tool creates and modifies HR lifecycle event cases (onboarding, offboarding, transfer, role change) in ServiceNow. Creating or completing such cases has significant HR consequences for employees — triggering or halting onboarding/offboarding workflows, access provisioning, and payroll changes. The primary actions are Write (create/modify records), though the downstream effects are high-severity.

From the tool's definition create_event — open a new lifecycle-event case for an employee (onboarding, offboarding, transfer, role change); complete_event — mark a lifecycle-event case as complete (closes the case and stops scheduled acti

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs snow_hr_lifecycle_event safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_hr_lifecycle_event, this is the rule to start with:

snow_hr_lifecycle_event Rate-limited

snow_hr_lifecycle_event stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "snow_hr_lifecycle_event": {
      "limits": [
        {
          "counter": "snow_hr_lifecycle_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Serac, apply this rule, and every snow_hr_lifecycle_event call is checked against it from then on.

FAQ

Questions about snow_hr_lifecycle_event

What does the snow_hr_lifecycle_event tool do? +

Unified tool for ServiceNow HR Lifecycle Events (LEM): manage lifecycle-event cases (sn_hr_le_case), their activities (sn_hr_le_activity), and the journey templates that drive them (sn_hr_core_journey_template, sn_hr_core_journey_activity). Actions: - create_event — open a new lifecycle-event case for an employee (onboarding, offboarding, transfer, role change). Optionally seeds activities from a journey template. - list_events — list lifecycle-event cases, filtered by employee, type, or state - complete_event — mark a lifecycle-event case as complete (closes the case and stops scheduled activities) - list_pending_for_employee — return open lifecycle-event activities assigned to an employee or owned by their case - trigger_journey — instantiate the activities defined on a journey template against an existing lifecycle-event case Use when: the agent needs to drive an end-to-end employee lifecycle event in HRSD. For a single ad-hoc HR ticket use snow_create_hr_case; for offboarding-only flows snow_employee_offboarding is a thinner wrapper around sn_hr_core_case. Requires the HR Lifecycle Events plugin (com.sn_hr_lifecycle_events). Tables may be absent on instances without the plugin, in which case the tool fails with a clear plugin-missing error. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on snow_hr_lifecycle_event? +

Register the Serac MCP server in PolicyLayer and add a rule for snow_hr_lifecycle_event: 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 Serac. Nothing to install.

What risk level is snow_hr_lifecycle_event? +

snow_hr_lifecycle_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit snow_hr_lifecycle_event? +

Yes. Add a rate_limit block to the snow_hr_lifecycle_event 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.

How do I block snow_hr_lifecycle_event completely? +

Set action: deny in the PolicyLayer policy for snow_hr_lifecycle_event. 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.

What MCP server provides snow_hr_lifecycle_event? +

snow_hr_lifecycle_event is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Serac, and thousands of servers like it.

This server

All 432 Serac tools →

Across the catalogue

calendar_create_event on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →