Build a DOL LCA-only employer profile with certification counts, wage statistics, top job titles, SOC codes, worksites, H-1B dependent, and willful violator flags.
AI agents call lca_employer_profile to retrieve information from DOL WHD MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates publicly available Department of Labor LCA (Labor Condition Application) data to build an employer profile. It performs read-only queries — collecting certification counts, wage statistics, job titles, SOC codes, and compliance flags — with no side effects, writes, or destructive actions.
From the tool's definition Build a DOL LCA-only employer profile with certification counts, wage statistics, top job titles, SOC codes, worksites, H-1B dependent, and willful violator flags.
Attacks that exploit this kind of access
Build a DOL LCA-only employer profile with certification counts, wage statistics, top job titles, SOC codes, worksites, H-1B dependent, and willful violator flags. It is categorised as a Read tool in the DOL WHD MCP MCP Server, which means it retrieves data without modifying state.
Register the DOL WHD MCP server in PolicyLayer and add a rule for lca_employer_profile: 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 DOL WHD MCP. Nothing to install.
lca_employer_profile 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 lca_employer_profile 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 lca_employer_profile. 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.
lca_employer_profile is provided by the DOL WHD MCP server (uhq-actual/dol_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 →