gov.fec.candidates
Search 53K+ US federal election candidates by name/cycle/office (House/Senate/Presidential)/state/party. Returns FEC candidate ID + filing dates. FEC public disclosure
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gov.fec.candidates.md
What gov.fec.candidates does on Apibase
AI agents call gov.fec.candidates 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 |
|---|---|---|---|
q | string | — | Free-text candidate name search (e.g. "Sanders", "Trump"). |
page | integer | — | Page number (default 1). |
cycle | integer | — | Election cycle year — even number (e.g. 2024, 2022, 2020). |
party | string | — | Party abbreviation (e.g. "REP", "DEM", "LIB", "GRE"). |
state | string | — | 2-letter state code (e.g. "CA", "TX"). |
office | string | — | Office: "H" House of Representatives, "S" Senate, "P" Presidential. |
per_page | integer | — | Per-page count (default 20, max 100). |
Parameters from the server's own tool schema.
Why gov.fec.candidates is rated Low
Tool queries public FEC disclosure data with no side effects or modifications.
From the tool's definition Search 53K+ US federal election candidates, returns FEC candidate ID + filing dates
Attacks that exploit this kind of access
The rule that runs gov.fec.candidates 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.candidates, this is the rule to start with:
gov.fec.candidates 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.candidates call is checked against it from then on.
Questions about gov.fec.candidates
Search 53K+ US federal election candidates by name/cycle/office (House/Senate/Presidential)/state/party. Returns FEC candidate ID + filing dates. 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.candidates accepts 7 parameters: q, page, cycle, party, state, office, per_page. 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.candidates: 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.candidates 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.candidates 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.candidates. 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.candidates 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