Medium Risk

export_records

Export WARN records in bulk. Requires Pro tier or higher. Returns up to 500 records with full field details. For CSV/Parquet downloads, use the REST API at /api/export/. Get your API key at warnfirehose.com/account Args: api_key: Your WARN Firehose API key (Pro tier required) state: Optional 2-le...

Risk signalsHandles credentials or secrets (api_key) · Bulk/mass operation — affects multiple targets

Part of the WARN Firehose — Labor Market Intelligence server.

export_records can modify WARN Firehose — Labor Market Intelligence data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE WARN FIREHOSE — LABOR MARKET INTELLIGENCE →

Free to start. No card required.

AI agents use export_records to create or modify resources in WARN Firehose — Labor Market Intelligence. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call export_records repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach WARN Firehose — Labor Market Intelligence.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_records": {
      "limits": [
        {
          "counter": "export_records_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full WARN Firehose — Labor Market Intelligence policy for all 12 tools.

Get this rule live on your own WARN Firehose — Labor Market Intelligence server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY WARN FIREHOSE — LABOR MARKET INTELLIGENCE →

View all 12 tools →

These attack patterns abuse exactly the kind of access export_records gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so export_records only ever does what you allow.

SECURE WARN FIREHOSE — LABOR MARKET INTELLIGENCE →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the export_records tool do? +

Export WARN records in bulk. Requires Pro tier or higher. Returns up to 500 records with full field details. For CSV/Parquet downloads, use the REST API at /api/export/. Get your API key at warnfirehose.com/account Args: api_key: Your WARN Firehose API key (Pro tier required) state: Optional 2-letter state code filter company: Optional company name filter (partial match) days: Look back this many days (default 90, max 730) limit: Max records to return (default 100, max 500). It is categorised as a Write tool in the WARN Firehose — Labor Market Intelligence MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_records? +

Register the WARN Firehose — Labor Market Intelligence MCP server in PolicyLayer and add a rule for export_records: 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.

What risk level is export_records? +

export_records is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit export_records? +

Yes. Add a rate_limit block to the export_records 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.

How do I block export_records completely? +

Set action: deny in the PolicyLayer policy for export_records. 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.

What MCP server provides export_records? +

export_records 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.

Enforce policy on every WARN Firehose — Labor Market Intelligence tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.