cfpb_complaint_aggregations
Aggregate complaint counts by a single facet (product, issue, company, state, company_response, or submitted_via). Useful for ranking companies by complaint volume or finding the most common issue categories.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cfpb-complaint-aggregations.md
What cfpb_complaint_aggregations does on Livedatalink
AI agents call cfpb_complaint_aggregations 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 |
|---|---|---|---|
facet | string | Yes | Field to aggregate by |
company | string | — | Optional company filter |
Parameters from the server's own tool schema.
Why cfpb_complaint_aggregations is rated Low
This tool performs data retrieval and aggregation only. It queries complaint data to generate statistics (counts grouped by facets like product, issue, company, state, etc.) with no capability to modify, delete, or execute operations. The read-only nature and lack of side effects clearly place it in the Read category with low severity, as misuse by an AI agent would only expose or analyze existing public data.
From the tool's definition Tool description states it 'aggregates complaint counts' and is 'useful for ranking companies by complaint volume or finding the most common issue categories.' These are read-only analytics operations that retrieve and summarize existing public complaint data…
Attacks that exploit this kind of access
The rule that runs cfpb_complaint_aggregations 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_aggregations, this is the rule to start with:
cfpb_complaint_aggregations 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_aggregations call is checked against it from then on.
Questions about cfpb_complaint_aggregations
Aggregate complaint counts by a single facet (product, issue, company, state, company_response, or submitted_via). Useful for ranking companies by complaint volume or finding the most common issue categories. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cfpb_complaint_aggregations accepts 2 parameters: facet, company. Required: facet. 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_aggregations: 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_aggregations 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_aggregations 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_aggregations. 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_aggregations 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