tengu_v3_workforce_layoff_screen
CROSS-SECTIONAL LAYOFF SCREEN — which listed companies filed WARN-Act layoff notices in the last N days, ranked by employees noticed. One row per ticker (company, filing count, employees noticed, first/latest event date, states touched, largest single filing) across the whole listed universe. Cal...
This record as markdown: /tools/tengu-mcp/tengu-v3-workforce-layoff-screen.md
What tengu_v3_workforce_layoff_screen does on Tengu
AI agents call tengu_v3_workforce_layoff_screen to retrieve information from Tengu without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
days | integer | — | |
limit | integer | — | |
state | string | — | |
min_employees | integer | — |
Parameters from the server's own tool schema.
Why tengu_v3_workforce_layoff_screen is rated Low
Even though tengu_v3_workforce_layoff_screen only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs tengu_v3_workforce_layoff_screen safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tengu, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tengu_v3_workforce_layoff_screen, this is the rule to start with:
tengu_v3_workforce_layoff_screen 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 Tengu, apply this rule, and every tengu_v3_workforce_layoff_screen call is checked against it from then on.
Questions about tengu_v3_workforce_layoff_screen
CROSS-SECTIONAL LAYOFF SCREEN — which listed companies filed WARN-Act layoff notices in the last N days, ranked by employees noticed. One row per ticker (company, filing count, employees noticed, first/latest event date, states touched, largest single filing) across the whole listed universe. Call it for 'who is cutting right now' — notices are filed weeks before the cut, so this surfaces restructurings before the press release. Only employers matched to a listed symbol appear; most WARN filers are private and are excluded by design. For one company's filings use /workforce/layoffs/{ticker}. It is categorised as a Read tool in the Tengu MCP Server, which means it retrieves data without modifying state.
tengu_v3_workforce_layoff_screen accepts 4 parameters: days, limit, state, min_employees. The full parameter table on this page comes from the server's own tool schema.
Register the Tengu MCP server in PolicyLayer and add a rule for tengu_v3_workforce_layoff_screen: 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 Tengu. Nothing to install.
tengu_v3_workforce_layoff_screen 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 tengu_v3_workforce_layoff_screen 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 tengu_v3_workforce_layoff_screen. 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.
tengu_v3_workforce_layoff_screen is provided by the Tengu MCP server (Hlobo-dev/tengu-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tengu, and thousands of servers like it.
This server
Across the catalogue