fetch_company_codes
AI agents call fetch_company_codes to retrieve information from mcpPaylocity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves company codes from the Paylocity API—a read-only operation. It has no side effects and merely queries reference data. While it accesses payroll system data (which could be considered sensitive), the risk is limited to information disclosure rather than modification, deletion, or financial transaction capability. Severity is low because company codes alone have minimal business impact if exposed.
From the tool's definition Tool is named 'fetch_company_codes' which follows the 'fetch_' pattern consistent with sibling tools (fetch_employee_details, fetch_employee_earnings, etc.).
Attacks that exploit this kind of access
fetch_company_codes. It is categorised as a Read tool in the mcpPaylocity MCP Server, which means it retrieves data without modifying state.
Register the mcpPaylocity MCP server in PolicyLayer and add a rule for fetch_company_codes: 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 mcpPaylocity. Nothing to install.
fetch_company_codes 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 fetch_company_codes 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 fetch_company_codes. 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.
fetch_company_codes is provided by the mcpPaylocity MCP server (mz462/mcppaylocity). 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 →