get_committee_flags

Check a campaign committee for compliance red flags including RFAIs (Requests for Additional Information from the FEC) and amended filings. Essential for identifying campaign finance compliance issues that merit closer research review.

Server Fec sh-patterson/fec-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_committee_flags does on Fec

AI agents call get_committee_flags to retrieve information from Fec without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_committee_flags needs a policy

This tool queries FEC campaign finance compliance data to surface red flags and filing amendments. It has no capability to create, modify, delete, or execute code. It presents minimal risk as a read-only operation that retrieves factual compliance information from a public database. The information returned may inform downstream decisions, but the tool itself only performs retrieval.

From the tool's definition The tool 'get_committee_flags' is described as checking a campaign committee for compliance red flags and RFAIs—it retrieves and queries compliance status data.

Questions about get_committee_flags

What does the get_committee_flags tool do? +

Check a campaign committee for compliance red flags including RFAIs (Requests for Additional Information from the FEC) and amended filings. Essential for identifying campaign finance compliance issues that merit closer research review. It is categorised as a Read tool in the Fec MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_committee_flags? +

Register the Fec MCP server in PolicyLayer and add a rule for get_committee_flags: 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 Fec. Nothing to install.

What risk level is get_committee_flags? +

get_committee_flags is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_committee_flags? +

Yes. Add a rate_limit block to the get_committee_flags 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.

How do I block get_committee_flags completely? +

Set action: deny in the PolicyLayer policy for get_committee_flags. 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.

What MCP server provides get_committee_flags? +

get_committee_flags is provided by the Fec MCP server (sh-patterson/fec-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.