fec_independent_expenditures
List independent expenditures (FEC Schedule E) supporting or opposing a candidate or made by a committee. Shows spender committee, amount, date, support/oppose, and description. Provide candidate_id or committee_id.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fec-independent-expenditures.md
What fec_independent_expenditures does on Livedatalink
AI agents call fec_independent_expenditures 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 |
|---|---|---|---|
cycle | number | — | Two-year election cycle (even year, e.g. 2024). Optional. |
limit | number | — | Maximum expenditures to return (default 20, max 100). |
candidate_id | string | — | FEC candidate ID the spending targets (e.g. 'P80001571'). Provide this or committee_id. |
committee_id | string | — | FEC committee ID of the spender (e.g. 'C00804856'). Provide this or candidate_id. |
Parameters from the server's own tool schema.
Why fec_independent_expenditures is rated Low
Even though fec_independent_expenditures 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 fec_independent_expenditures 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 fec_independent_expenditures, this is the rule to start with:
fec_independent_expenditures 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 fec_independent_expenditures call is checked against it from then on.
Questions about fec_independent_expenditures
List independent expenditures (FEC Schedule E) supporting or opposing a candidate or made by a committee. Shows spender committee, amount, date, support/oppose, and description. Provide candidate_id or committee_id. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fec_independent_expenditures accepts 4 parameters: cycle, limit, candidate_id, committee_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 fec_independent_expenditures: 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.
fec_independent_expenditures 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 fec_independent_expenditures 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 fec_independent_expenditures. 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.
fec_independent_expenditures 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