Get only the custom fields from an employee
AI agents call get_employee_custom_fields 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 is a read-only operation that retrieves custom field data associated with an employee record. It has no side effects, creates no new data, and does not modify existing records. While the Paylocity context involves sensitive HR/financial data, the automatic redaction of sensitive information (SSNs, bank account numbers) as noted in the server description mitigates exposure risk.
From the tool's definition Tool name contains 'get' and description explicitly states 'Get only the custom fields from an employee', indicating retrieval of data without modification.
Attacks that exploit this kind of access
Get only the custom fields from an employee. 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 get_employee_custom_fields: 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.
get_employee_custom_fields 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 get_employee_custom_fields 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 get_employee_custom_fields. 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.
get_employee_custom_fields 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 →