gov.fec.super_pac_spending
Schedule E independent expenditures — Super PAC spending supporting/opposing specific federal candidates. Filter by cycle, candidate ID, or support/oppose direction. FEC public disclosure
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gov.fec.super-pac-spending.md
What gov.fec.super_pac_spending does on Apibase
AI agents call gov.fec.super_pac_spending 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). |
candidate_id | string | — | FEC candidate ID (from fec.candidates) — return only expenditures targeting this candidate. |
support_oppose | string | — | "S" support / "O" oppose. If omitted, both directions returned. |
Parameters from the server's own tool schema.
Why gov.fec.super_pac_spending is rated Low
Retrieves publicly disclosed FEC campaign finance data; no modifications, deletions, or financial transactions initiated.
From the tool's definition Schedule E independent expenditures — Super PAC spending supporting/opposing specific federal candidates. Filter by cycle, candidate ID
Attacks that exploit this kind of access
The rule that runs gov.fec.super_pac_spending 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.super_pac_spending, this is the rule to start with:
gov.fec.super_pac_spending 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.super_pac_spending call is checked against it from then on.
Questions about gov.fec.super_pac_spending
Schedule E independent expenditures — Super PAC spending supporting/opposing specific federal candidates. Filter by cycle, candidate ID, or support/oppose direction. 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.super_pac_spending accepts 5 parameters: page, cycle, per_page, candidate_id, support_oppose. 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.super_pac_spending: 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.super_pac_spending 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.super_pac_spending 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.super_pac_spending. 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.super_pac_spending 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