snow_hr_profile_manage
Unified tool for ServiceNow HR employee profiles (sn_hr_core_profile). Searches join through profile.user reference for sys_user fields (department, email, active). Actions: - get_profile — fetch a profile by sys_id, user sys_id, or employee_number - update_profile — patch profile fields (employm...
This record as markdown: /tools/serac/snow-hr-profile-manage.md
What snow_hr_profile_manage does on Serac
AI agents use snow_hr_profile_manage 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.
Why snow_hr_profile_manage is rated Medium
The tool primarily serves read operations (get_profile, search_employees), but the update_profile action creates reversible modifications to canonical HR employee records in ServiceNow. This is Write rather than Destructive because updates are patchable and not permanent deletions.
From the tool's definition Tool includes 'update_profile — patch profile fields' action that modifies employee records (employment_type, position, primary_job, location, personal_email, work_mobile, mobile_phone, im_name).
Attacks that exploit this kind of access
The rule that runs snow_hr_profile_manage 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_profile_manage, this is the rule to start with:
snow_hr_profile_manage 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Serac, apply this rule, and every snow_hr_profile_manage call is checked against it from then on.
Questions about snow_hr_profile_manage
Unified tool for ServiceNow HR employee profiles (sn_hr_core_profile). Searches join through profile.user reference for sys_user fields (department, email, active). Actions: - get_profile — fetch a profile by sys_id, user sys_id, or employee_number - update_profile — patch profile fields (employment_type, position, primary_job, location, personal_email, work_mobile, mobile_phone, im_name) - search_employees — search profiles by name, email, department, or employee_number Use when: the agent needs to read or maintain the canonical employee record used across all HR cases. Companion tools: snow_create_hr_case (opens HR tickets against a profile), snow_create_hr_task (creates task work on a case), snow_hr_lifecycle_event (drives onboarding/offboarding flows). Requires the HR Core plugin (com.sn_hr_core). When the plugin is missing the underlying tables don. 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.
Register the Serac MCP server in PolicyLayer and add a rule for snow_hr_profile_manage: 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.
snow_hr_profile_manage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the snow_hr_profile_manage 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 snow_hr_profile_manage. 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.
snow_hr_profile_manage 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.
More on Serac, and thousands of servers like it.
This server
Across the catalogue