fdic_deposits
Branch-office deposit data from the FDIC Summary of Deposits (annual snapshot). Returns deposits per branch sorted by deposit volume, useful for measuring local-market banking concentration.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fdic-deposits.md
What fdic_deposits does on Livedatalink
AI agents call fdic_deposits 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 |
|---|---|---|---|
city | string | — | City name |
limit | number | — | Max branches (default 25) |
state | string | — | Two-letter state code |
Parameters from the server's own tool schema.
Why fdic_deposits is rated Low
This tool queries and retrieves historical FDIC deposit statistics to support analysis of banking market concentration. It performs no write, delete, execute, or financial transaction operations. The data returned is aggregated public information suitable for research and analysis. No side effects or irreversible changes are possible.
From the tool's definition Tool description states 'Returns deposits per branch sorted by deposit volume' — a retrieval and reporting operation with no modification, deletion, or execution capability. FDIC Summary of Deposits data is public financial reporting data.
Attacks that exploit this kind of access
The rule that runs fdic_deposits 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_deposits, this is the rule to start with:
fdic_deposits 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_deposits call is checked against it from then on.
Questions about fdic_deposits
Branch-office deposit data from the FDIC Summary of Deposits (annual snapshot). Returns deposits per branch sorted by deposit volume, useful for measuring local-market banking concentration. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fdic_deposits accepts 3 parameters: city, limit, state. 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_deposits: 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_deposits 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_deposits 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_deposits. 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_deposits 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