lobbying_contributions
Search LDA contribution reports (political contributions disclosed by lobbyists/registrants). Filter by year, registrant, or lobbyist name.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/lobbying-contributions.md
What lobbying_contributions does on Livedatalink
AI agents call lobbying_contributions 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 |
|---|---|---|---|
page_size | number | — | Results per page (default 20). |
filing_year | number | — | Filing year, e.g. 2025. |
lobbyist_name | string | — | Lobbyist name, partial match. |
registrant_name | string | — | Registrant (firm) name, partial match. |
Parameters from the server's own tool schema.
Why lobbying_contributions is rated Low
Even though lobbying_contributions only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs lobbying_contributions 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 lobbying_contributions, this is the rule to start with:
lobbying_contributions 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 lobbying_contributions call is checked against it from then on.
Questions about lobbying_contributions
Search LDA contribution reports (political contributions disclosed by lobbyists/registrants). Filter by year, registrant, or lobbyist name. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
lobbying_contributions accepts 4 parameters: page_size, filing_year, lobbyist_name, registrant_name. 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 lobbying_contributions: 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.
lobbying_contributions 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 lobbying_contributions 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 lobbying_contributions. 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.
lobbying_contributions 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