stocks.h1b-visas
US work-visa (H-1B and related) applications filed by a public company, sourced from Department of Labor LCA disclosures. Pass ticker and optionally a from/to window (YYYY-MM-DD; defaults to ~2 years); returns each application with job title, SOC code, visa class, case status, wage range, worksit...
This record as markdown: /tools/io-github-2s-io-mcp/stocks.h1b-visas.md
What stocks.h1b-visas does on Mcp
AI agents call stocks.h1b-visas to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why stocks.h1b-visas is rated Low
This tool fetches read-only public government data (H-1B visa applications from DOL LCA disclosures) for a given ticker and date range. It has no side effects, does not modify any data, and returns informational records. The pay-per-call nature adds minor financial cost per invocation, but the tool itself is a data retrieval operation. Severity is low as the data is already public and misuse potential is minimal.
From the tool's definition 'returns each application with job title, SOC code, visa class, case status, wage range, worksite city/state, employment dates, and case number' — purely retrieves and returns publicly available Department of Labor LCA disclosure data
Attacks that exploit this kind of access
The rule that runs stocks.h1b-visas safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stocks.h1b-visas, this is the rule to start with:
stocks.h1b-visas is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every stocks.h1b-visas call is checked against it from then on.
Questions about stocks.h1b-visas
US work-visa (H-1B and related) applications filed by a public company, sourced from Department of Labor LCA disclosures. Pass ticker and optionally a from/to window (YYYY-MM-DD; defaults to ~2 years); returns each application with job title, SOC code, visa class, case status, wage range, worksite city/state, employment dates, and case number. Use it as a hiring/headcount signal. Data by Finnhub. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for stocks.h1b-visas: 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 Mcp. Nothing to install.
stocks.h1b-visas 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 stocks.h1b-visas 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 stocks.h1b-visas. 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.
stocks.h1b-visas is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue