fec_candidate_details
Get full detail for a single federal candidate by FEC candidate_id (e.g. 'P80001571'). Includes office, party, status, election years, and mailing address. Use fec_candidate_search to find the candidate_id.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fec-candidate-details.md
What fec_candidate_details does on Livedatalink
AI agents call fec_candidate_details 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 |
|---|---|---|---|
candidate_id | string | Yes | FEC candidate ID (e.g. 'P80001571', 'S2MA00170'). |
Parameters from the server's own tool schema.
Why fec_candidate_details is rated Low
This is a straightforward data retrieval tool that queries and returns public federal election data from FEC sources. It has no side effects, does not modify or delete data, and does not execute external operations. The information returned (candidate office, party affiliation, etc.) is publicly available electoral information.
From the tool's definition Tool retrieves candidate details by ID and returns informational fields: office, party, status, election years, and mailing address. No modification, deletion, or execution capabilities described.
Attacks that exploit this kind of access
The rule that runs fec_candidate_details 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_candidate_details, this is the rule to start with:
fec_candidate_details 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_candidate_details call is checked against it from then on.
Questions about fec_candidate_details
Get full detail for a single federal candidate by FEC candidate_id (e.g. 'P80001571'). Includes office, party, status, election years, and mailing address. Use fec_candidate_search to find the candidate_id. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fec_candidate_details accepts 1 parameter: candidate_id. Required: candidate_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_candidate_details: 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_candidate_details 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_candidate_details 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_candidate_details. 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_candidate_details 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