gov.fec-candidate
Search US federal political candidates via OpenFEC. Filter by q (name), candidate ID, state/district, party, office (P/S/H), cycle, electionYear, hasRaised. Returns FEC candidate ID linkable to /api/gov/fec-committee.
This record as markdown: /tools/io-github-2s-io-mcp/gov.fec-candidate.md
What gov.fec-candidate does on Mcp
AI agents call gov.fec-candidate to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gov.fec-candidate is rated Low
This tool retrieves publicly available Federal Election Commission candidate information via search and filtering. It returns data (candidate IDs) without creating, modifying, deleting, or moving money. The operation is read-only with no side effects on any system state. The severity is low because misuse would only expose already-public political candidate information.
From the tool's definition The tool 'Search US federal political candidates via OpenFEC' with parameters like q (name), candidate ID, state/district, party, office, cycle, electionYear, hasRaised describes a query operation that 'Returns FEC candidate ID' for linking to other data.
Attacks that exploit this kind of access
The rule that runs gov.fec-candidate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gov.fec-candidate, this is the rule to start with:
gov.fec-candidate 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 Mcp, apply this rule, and every gov.fec-candidate call is checked against it from then on.
Questions about gov.fec-candidate
Search US federal political candidates via OpenFEC. Filter by q (name), candidate ID, state/district, party, office (P/S/H), cycle, electionYear, hasRaised. Returns FEC candidate ID linkable to /api/gov/fec-committee. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for gov.fec-candidate: 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 Mcp. Nothing to install.
gov.fec-candidate 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-candidate 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-candidate. 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-candidate is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue