cfpb_complaint_detail
Fetch a single CFPB complaint by complaint_id. Returns the full record including narrative if consented.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cfpb-complaint-detail.md
What cfpb_complaint_detail does on Livedatalink
AI agents call cfpb_complaint_detail 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 |
|---|---|---|---|
complaint_id | string | Yes | CFPB complaint ID |
Parameters from the server's own tool schema.
Why cfpb_complaint_detail is rated Low
This tool retrieves publicly available CFPB (Consumer Financial Protection Bureau) complaint records by ID. It performs a read-only query operation with no side effects, data modification, or execution capability. The blast radius of misuse is minimal—an agent could retrieve complaint details it shouldn't have access to, but cannot modify, delete, or create records.
From the tool's definition Tool name includes 'detail' and description states 'Fetch a single CFPB complaint' with 'Returns the full record'. The verb 'Fetch' and the retrieval-only nature indicate data querying without modification.
Attacks that exploit this kind of access
The rule that runs cfpb_complaint_detail 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_detail, this is the rule to start with:
cfpb_complaint_detail 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_detail call is checked against it from then on.
Questions about cfpb_complaint_detail
Fetch a single CFPB complaint by complaint_id. Returns the full record including narrative if consented. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cfpb_complaint_detail accepts 1 parameter: complaint_id. Required: complaint_id. 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_detail: 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_detail 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_detail 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_detail. 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_detail 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