fdic_failures
List FDIC bank failures. Filter by state and/or date range. Returns failure date, institution name, location, estimated cost, and resolution type. Sorted most-recent first. Use this for systemic-risk research, historical bank-stability analysis, or compliance work.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fdic-failures.md
What fdic_failures does on Livedatalink
AI agents call fdic_failures to retrieve information from Livedatalink 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 |
|---|---|---|---|
limit | number | — | Max results (default 25) |
state | string | — | Two-letter state code |
offset | number | — | Pagination offset |
end_date | string | — | End date YYYY-MM-DD |
start_date | string | — | Start date YYYY-MM-DD |
Parameters from the server's own tool schema.
Why fdic_failures is rated Low
This tool retrieves and queries publicly available historical FDIC data. It performs read-only operations (list, filter, return) with no side effects. The data returned is factual, historical information about past bank failures—already public knowledge. There is no capability to modify records, execute code, delete data, or commit financial transactions.
From the tool's definition Tool description explicitly states 'List FDIC bank failures' with filtering by state and date range. Returns historical data: 'failure date, institution name, location, estimated cost, and resolution type.' No modification, deletion, or execution capability…
Attacks that exploit this kind of access
The rule that runs fdic_failures safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fdic_failures, this is the rule to start with:
fdic_failures 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 Livedatalink, apply this rule, and every fdic_failures call is checked against it from then on.
Questions about fdic_failures
List FDIC bank failures. Filter by state and/or date range. Returns failure date, institution name, location, estimated cost, and resolution type. Sorted most-recent first. Use this for systemic-risk research, historical bank-stability analysis, or compliance work. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fdic_failures accepts 5 parameters: limit, state, offset, end_date, start_date. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for fdic_failures: 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 Livedatalink. Nothing to install.
fdic_failures 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 fdic_failures 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 fdic_failures. 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.
fdic_failures is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue