fec_committee_search
Search FEC-registered political committees (campaign committees, PACs, party committees, Super PACs) by name, state, or committee type. Returns committee IDs.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fec-committee-search.md
What fec_committee_search does on Livedatalink
AI agents call fec_committee_search 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 committees to return (default 20, max 100). |
query | string | — | Committee name fragment. Optional. |
state | string | — | Two-letter state code to filter by. Optional. |
committee_type | string | — | Committee type code: 'P' (President), 'S' (Senate), 'H' (House), 'N'/'Q' (PAC), 'O' (Super PAC), 'X'/'Y' (party). Optional. |
Parameters from the server's own tool schema.
Why fec_committee_search is rated Low
Even though fec_committee_search 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_committee_search 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_committee_search, this is the rule to start with:
fec_committee_search 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_committee_search call is checked against it from then on.
Questions about fec_committee_search
Search FEC-registered political committees (campaign committees, PACs, party committees, Super PACs) by name, state, or committee type. Returns committee IDs. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fec_committee_search accepts 5 parameters: cycle, limit, query, state, committee_type. 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_committee_search: 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_committee_search 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_committee_search 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_committee_search. 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_committee_search 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