get_campaign_filings
AI agents call get_campaign_filings to retrieve information from FEC Campaign Finance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Campaign finance filings are public records. The tool name and server context indicate read-only data retrieval from the OpenFEC API. No modification, execution of code, deletion, or financial transactions occur. Confidence is reduced slightly (0.85 rather than 0.95) because the description is empty, introducing minor ambiguity, but the naming pattern and server purpose make Read the clear classification.
From the tool's definition Tool name is 'get_campaign_filings' with an empty description. Context: this server is dedicated to 'investigating US federal campaign finance' through the OpenFEC API.
Attacks that exploit this kind of access
get_campaign_filings. It is categorised as a Read tool in the FEC Campaign Finance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FEC Campaign Finance MCP Server MCP server in PolicyLayer and add a rule for get_campaign_filings: 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 Campaign Finance MCP Server. Nothing to install.
get_campaign_filings 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_campaign_filings 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_campaign_filings. 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_campaign_filings is provided by the FEC Campaign Finance MCP Server MCP server (reichaves/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 →