cfpb_state_complaints
Complaint counts and percentages per US state, with optional product filter and date range. Useful for state-level financial-consumer risk maps.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cfpb-state-complaints.md
What cfpb_state_complaints does on Livedatalink
AI agents call cfpb_state_complaints 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 |
|---|---|---|---|
product | string | — | Optional product filter |
date_received_max | string | — | YYYY-MM-DD upper bound |
date_received_min | string | — | YYYY-MM-DD lower bound |
Parameters from the server's own tool schema.
Why cfpb_state_complaints is rated Low
This tool queries aggregated, publicly available financial-consumer complaint statistics by state. It has no side effects—it neither creates, modifies, deletes data, nor executes code or financial transactions. The optional filters (product, date range) are standard read-operation parameters. Even in financial domain context, a complaints statistics query is a Read operation with low risk if misused by an agent.
From the tool's definition Tool retrieves 'complaint counts and percentages per US state' with optional filters; no modification, deletion, or execution capability described. The verb phrases 'complaint counts' and 'percentages' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs cfpb_state_complaints 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 cfpb_state_complaints, this is the rule to start with:
cfpb_state_complaints 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 cfpb_state_complaints call is checked against it from then on.
Questions about cfpb_state_complaints
Complaint counts and percentages per US state, with optional product filter and date range. Useful for state-level financial-consumer risk maps. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cfpb_state_complaints accepts 3 parameters: product, date_received_max, date_received_min. 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 cfpb_state_complaints: 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.
cfpb_state_complaints 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 cfpb_state_complaints 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 cfpb_state_complaints. 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.
cfpb_state_complaints 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