gov.fec.committee_totals
Receipts, disbursements, and cash-on-hand for US political committees (PACs, parties, candidate committees). Filter by cycle and committee type. FEC public disclosure
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gov.fec.committee-totals.md
What gov.fec.committee_totals does on Apibase
AI agents call gov.fec.committee_totals 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 |
|---|---|---|---|
page | integer | — | Page number (default 1). |
cycle | integer | — | Election cycle year (e.g. 2024). |
per_page | integer | — | Per-page count (default 20, max 100). |
committee_type | string | — | Committee type code: "P" Presidential, "H" House, "S" Senate, "X" Party, "Y" Party-Qualified, "N" PAC, "Q" PAC-Qualified, "O" Super PAC. |
Parameters from the server's own tool schema.
Why gov.fec.committee_totals is rated Low
Retrieves publicly disclosed financial data about political committees; no modification or side effects.
From the tool's definition Receipts, disbursements, cash-on-hand for US political committees. FEC public disclosure.
Attacks that exploit this kind of access
The rule that runs gov.fec.committee_totals 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 gov.fec.committee_totals, this is the rule to start with:
gov.fec.committee_totals 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 Apibase, apply this rule, and every gov.fec.committee_totals call is checked against it from then on.
Questions about gov.fec.committee_totals
Receipts, disbursements, and cash-on-hand for US political committees (PACs, parties, candidate committees). Filter by cycle and committee type. FEC public disclosure. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gov.fec.committee_totals accepts 4 parameters: page, cycle, per_page, committee_type. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for gov.fec.committee_totals: 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.
gov.fec.committee_totals 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 gov.fec.committee_totals 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 gov.fec.committee_totals. 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.
gov.fec.committee_totals 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.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue