Add a new employee to the system (onboarding). Creates the employee record with personal info, job details, and compensation. SSN is required by Paylocity but will not be stored in conversation — pass it directly and it will be sent encrypted. Returns the new employee ID.
AI agents use add_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.
The tool performs a create operation on employee records in an HR/payroll system. This falls squarely into the Write category as it creates new data records reversibly. While it touches sensitive personal and financial information (SSN, compensation details), the action is not Financial (no money movement) nor Destructive (the record can be removed or corrected).
From the tool's definition Tool creates a new employee record with personal info, job details, and compensation. Description explicitly states 'Add a new employee to the system (onboarding)' and 'Creates the employee record'.
Attacks that exploit this kind of access
Add a new employee to the system (onboarding). Creates the employee record with personal info, job details, and compensation. SSN is required by Paylocity but will not be stored in conversation — pass it directly and it will be sent encrypted. Returns the new employee ID. 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_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_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_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_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_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 →