cfpb_complaint_trends
Time-series trends of complaint volume. lens=overview shows total complaints over time; lens=product shows by product; lens=company shows by company; lens=issue shows by issue. Interval can be month, quarter, or year.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cfpb-complaint-trends.md
What cfpb_complaint_trends does on Livedatalink
AI agents call cfpb_complaint_trends 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 |
|---|---|---|---|
lens | string | Yes | Trend dimension |
product | string | — | Filter to a specific product |
sub_lens | string | — | Optional sub-dimension |
trend_depth | number | — | Top N to track (default 5) |
trend_interval | string | — | Time bucket size |
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_complaint_trends is rated Low
Even though cfpb_complaint_trends only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs cfpb_complaint_trends 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_complaint_trends, this is the rule to start with:
cfpb_complaint_trends 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_complaint_trends call is checked against it from then on.
Questions about cfpb_complaint_trends
Time-series trends of complaint volume. lens=overview shows total complaints over time; lens=product shows by product; lens=company shows by company; lens=issue shows by issue. Interval can be month, quarter, or year. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cfpb_complaint_trends accepts 7 parameters: lens, product, sub_lens, trend_depth, trend_interval, date_received_max, date_received_min. Required: lens. 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_complaint_trends: 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_complaint_trends 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_complaint_trends 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_complaint_trends. 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_complaint_trends 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