fdic_history
Institution history events for a specific bank by CERT: mergers, acquisitions, name changes, charter conversions, failures. Returns most-recent first.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fdic-history.md
What fdic_history does on Livedatalink
AI agents call fdic_history 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 |
|---|---|---|---|
cert | number | Yes | FDIC Certificate Number |
limit | number | — | Max events (default 25) |
Parameters from the server's own tool schema.
Why fdic_history is rated Low
This tool queries historical banking institution records by CERT identifier. It is a pure read operation that retrieves archived or reference data about past events. There are no side effects, no data modifications, no code execution, and no financial transactions involved.
From the tool's definition Tool retrieves 'Institution history events' including 'mergers, acquisitions, name changes, charter conversions, failures' — all historical data queries with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs fdic_history 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_history, this is the rule to start with:
fdic_history 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_history call is checked against it from then on.
Questions about fdic_history
Institution history events for a specific bank by CERT: mergers, acquisitions, name changes, charter conversions, failures. Returns most-recent first. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fdic_history accepts 2 parameters: cert, limit. Required: cert. 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_history: 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_history 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_history 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_history. 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_history 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