Start onboarding for a new hire — pushes the employee through the self-service onboarding workflow (forms, I-9, W-4, direct deposit setup) instead of creating a bare payroll record. Use add_employee if you want to skip onboarding and create the record directly. NOTE: This endpoint may require add...
AI agents use add_onboarding_employee to create or update resources in Paylocity MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Paylocity MCP Server environment.
This tool creates new employee records and initiates onboarding workflows, which modifies company HR/payroll data. While reversible (employees can be removed or records updated), it creates persistent employee records, onboarding forms, and links to financial systems (direct deposit setup).
From the tool's definition Tool description explicitly states it 'Start onboarding for a new hire — pushes the employee through the self-service onboarding workflow (forms, I-9, W-4, direct deposit setup)' and contrasts with add_employee by noting it creates records rather than…
Attacks that exploit this kind of access
Start onboarding for a new hire — pushes the employee through the self-service onboarding workflow (forms, I-9, W-4, direct deposit setup) instead of creating a bare payroll record. Use add_employee if you want to skip onboarding and create the record directly. NOTE: This endpoint may require additional permissions on your WebLink API key. If it fails with 403/404, your key likely needs the Onboarding scope enabled — contact your Paylocity rep. It is categorised as a Write tool in the Paylocity MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Paylocity MCP Server MCP server in PolicyLayer and add a rule for add_onboarding_employee: 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 Paylocity MCP Server. Nothing to install.
add_onboarding_employee 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 add_onboarding_employee 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 add_onboarding_employee. 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.
add_onboarding_employee is provided by the Paylocity MCP Server MCP server (lucid-drone-technologies/paylocity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →