Search the employee directory by name, job title, email, or employee ID. Returns matching employees with basic info (name, title, department, status, supervisor). Use this first to find someone
AI agents call search_employees to retrieve information from Paylocity MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves employee information from a directory without side effects. While employee data can be sensitive, the search is limited to basic organizational information (name, title, department, status, supervisor). The description explicitly notes the server has 'automated data protection that redacts sensitive information like SSNs and bank account numbers,' further limiting exposure.
From the tool's definition Tool description states it 'Search[es] the employee directory' and 'Returns matching employees with basic info (name, title, department, status, supervisor).' The verb 'search' and 'returns' indicate data retrieval with no modification.
Attacks that exploit this kind of access
Search the employee directory by name, job title, email, or employee ID. Returns matching employees with basic info (name, title, department, status, supervisor). Use this first to find someone. It is categorised as a Read tool in the Paylocity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Paylocity MCP Server MCP server in PolicyLayer and add a rule for search_employees: 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.
search_employees 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 search_employees 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 search_employees. 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.
search_employees 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 →