fdic.institutions.failures
Query the FDIC failed bank list. Returns 4,100+ historical bank failures with failure date, assets at closure, acquiring institution, and estimated loss to the Deposit Insurance Fund. Covers all failures since 1934.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/fdic.institutions.failures.md
What fdic.institutions.failures does on Apibase
AI agents call fdic.institutions.failures to retrieve information from Apibase 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 | integer | — | Number of results to return, max 50 (default 10) |
state | string | — | Two-letter US state code filter (e.g. "CA", "NY", "TX") |
Parameters from the server's own tool schema.
Why fdic.institutions.failures is rated Low
Retrieves historical public FDIC data without side effects or modification capability.
From the tool's definition Query the FDIC failed bank list. Returns historical bank failures.
Attacks that exploit this kind of access
The rule that runs fdic.institutions.failures safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fdic.institutions.failures, this is the rule to start with:
fdic.institutions.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 Apibase, apply this rule, and every fdic.institutions.failures call is checked against it from then on.
Questions about fdic.institutions.failures
Query the FDIC failed bank list. Returns 4,100+ historical bank failures with failure date, assets at closure, acquiring institution, and estimated loss to the Deposit Insurance Fund. Covers all failures since 1934. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
fdic.institutions.failures accepts 2 parameters: limit, state. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for fdic.institutions.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 Apibase. Nothing to install.
fdic.institutions.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.institutions.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.institutions.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.institutions.failures is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue