cfpb-complaints.complaints.trends

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 80 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/cfpb-complaints.complaints.trends.md

WHAT IT DOES

What cfpb-complaints.complaints.trends does on Apibase

AI agents call cfpb-complaints.complaints.trends 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
`lens`	string	—	Trend breakdown dimension (default "overview" — total volume only, no `sub_lens` needed). "product"/"issue"/"company" require `sub_lens` to be set, or upstream
`state`	string	—	Two-letter US state or territory postal abbreviation (e.g. "CA", "NY", "PR").
`company`	string	—	Exact registered company name as CFPB records it, typically uppercase with legal suffix (e.g. "EQUIFAX, INC.", "WELLS FARGO & COMPANY", "BANK OF AMERICA, NATION
`product`	string	—	Exact CFPB product category — must match verbatim, e.g. "Credit reporting or other personal consumer reports", "Debt collection", "Mortgage", "Checking or savin
`date_max`	string	—	End of the date range, format YYYY-MM-DD.
`date_min`	string	—	Start of the date range, format YYYY-MM-DD.
`sub_lens`	string	—	Secondary breakdown required when `lens` is not "overview". Valid per lens: product→(sub_product, issue, company, tags); issue→(product, sub_issue, company, tag
`trend_interval`	string	—	Time bucket size for the trend series (default "month").

Parameters from the server's own tool schema.

RISK

Why cfpb-complaints.complaints.trends is rated Low

Retrieves historical complaint data without modifying or executing external operations; read-only analytical query.

From the tool's definition Get the time-series trend of CFPB consumer complaint volume

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cfpb-complaints.complaints.trends 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 cfpb-complaints.complaints.trends, this is the rule to start with:

cfpb-complaints.complaints.trends Allowed

cfpb-complaints.complaints.trends is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cfpb-complaints.complaints.trends": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every cfpb-complaints.complaints.trends call is checked against it from then on.

FAQ

Questions about cfpb-complaints.complaints.trends

What does the cfpb-complaints.complaints.trends tool do? +

Get the time-series trend of CFPB consumer complaint volume — weekly, monthly, or yearly buckets — optionally filtered by product, company, or US state, and optionally broken down (e.g. by sub-product or issue when a lens is specified). Useful for spotting spikes in complaints against a company or product over time. Data: consumerfinance.gov (CFPB), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does cfpb-complaints.complaints.trends accept? +

cfpb-complaints.complaints.trends accepts 8 parameters: lens, state, company, product, date_max, date_min, sub_lens, trend_interval. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on cfpb-complaints.complaints.trends? +

Register the Apibase MCP server in PolicyLayer and add a rule for cfpb-complaints.complaints.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 Apibase. Nothing to install.

What risk level is cfpb-complaints.complaints.trends? +

cfpb-complaints.complaints.trends is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cfpb-complaints.complaints.trends? +

Yes. Add a rate_limit block to the cfpb-complaints.complaints.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.

How do I block cfpb-complaints.complaints.trends completely? +

Set action: deny in the PolicyLayer policy for cfpb-complaints.complaints.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.

What MCP server provides cfpb-complaints.complaints.trends? +

cfpb-complaints.complaints.trends 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →