AI agents call lookup_company to retrieve information from H1b without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical visa sponsorship statistics from public data sources. It performs a lookup operation that queries existing records and returns counts without any side effects, data modification, or operational impact. The data is public (Department of Labor records) and the operation is read-only, making it a low-risk Read category tool.
From the tool's definition Tool description states it 'Check if a company sponsors H1B visas' and 'Returns certified/denied/withdrawn counts' — purely retrieving and querying public Department of Labor records with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Check if a company sponsors H1B visas. Returns certified/denied/withdrawn counts. It is categorised as a Read tool in the H1b MCP Server, which means it retrieves data without modifying state.
Register the H1b MCP server in PolicyLayer and add a rule for lookup_company: 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 H1b. Nothing to install.
lookup_company 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 lookup_company 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 lookup_company. 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.
lookup_company is provided by the H1b MCP server (yoginoit39/jobsearch-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 →