Get pay statement data for an employee by year. Returns both summary (gross pay, net pay, hours, direct deposit amounts) and line-item details (each tax, deduction, and earning). Optionally filter to a specific check date.
AI agents call get_pay_statements 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 only queries and retrieves existing pay statement data for an employee. It performs no writes, deletes, or external operations. While pay statements contain sensitive financial information, the tool itself is a read-only query operation. The server includes automated redaction of sensitive data (SSNs, bank account numbers) before the model receives it, further limiting exposure.
From the tool's definition Tool name is 'get_pay_statements' and description explicitly states it 'Returns...summary...and line-item details' of pay statements. The verb 'Get' and 'Returns' indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Get pay statement data for an employee by year. Returns both summary (gross pay, net pay, hours, direct deposit amounts) and line-item details (each tax, deduction, and earning). Optionally filter to a specific check date. 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_pay_statements: 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_pay_statements 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_pay_statements 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_pay_statements. 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_pay_statements 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 →