Retrieve itemized contributions (Schedule A) received by a campaign committee. Shows individual and organizational donors, amounts, and contributor details. Automatically classifies PAC contributions by type (Corporate, Labor, Trade, Leadership PAC) for deeper analysis. Supports filtering by amou...
AI agents call get_receipts 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.
This tool queries and retrieves existing campaign finance data from the OpenFEC API without modifying, deleting, or executing operations. It enables analysis of public FEC records but does not create, alter, or destroy data. The filtering and classification features support analytical queries rather than data mutation.
From the tool's definition Retrieve itemized contributions (Schedule A)" and "Shows individual and organizational donors, amounts, and contributor details" indicate read-only data retrieval with no side effects. The tool "Supports filtering by amount threshold" for analysis only.
Attacks that exploit this kind of access
Retrieve itemized contributions (Schedule A) received by a campaign committee. Shows individual and organizational donors, amounts, and contributor details. Automatically classifies PAC contributions by type (Corporate, Labor, Trade, Leadership PAC) for deeper analysis. Supports filtering by amount threshold for researching significant contributions and campaign finance patterns. It is categorised as a Read tool in the Fec MCP Server, which means it retrieves data without modifying state.
Register the Fec MCP server in PolicyLayer and add a rule for get_receipts: 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.
get_receipts 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 get_receipts 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 get_receipts. 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.
get_receipts 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.
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 →