Search WARN Act layoff notices by company name, city, or keyword. Args: query: Search term (company name, city, etc.) state: Optional 2-letter state code to filter (e.g. CA, TX, NY) limit: Max results to return (default 20, max 100) api_key: Optional API key for higher rate limits
Risk signalsAccepts freeform code/query input (query) · Handles credentials or secrets (api_key)
Part of the WARN Firehose — Labor Market Intelligence server.
Free to start. No card required.
AI agents call search_layoffs to retrieve information from WARN Firehose — Labor Market Intelligence without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though search_layoffs only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"search_layoffs": {}
}
}See the full WARN Firehose — Labor Market Intelligence policy for all 12 tools.
These attack patterns abuse exactly the kind of access search_layoffs gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search WARN Act layoff notices by company name, city, or keyword. Args: query: Search term (company name, city, etc.) state: Optional 2-letter state code to filter (e.g. CA, TX, NY) limit: Max results to return (default 20, max 100) api_key: Optional API key for higher rate limits. It is categorised as a Read tool in the WARN Firehose — Labor Market Intelligence MCP Server, which means it retrieves data without modifying state.
Register the WARN Firehose — Labor Market Intelligence MCP server in PolicyLayer and add a rule for search_layoffs: 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 WARN Firehose — Labor Market Intelligence. Nothing to install.
search_layoffs 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 search_layoffs 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 search_layoffs. 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.
search_layoffs is provided by the WARN Firehose — Labor Market Intelligence MCP server (https://warnfirehose.com/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 WARN Firehose — Labor Market Intelligence tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.