lobbying_lobbyists
Search individual lobbyists by name (and optionally by their registrant firm). Returns lobbyist records with their associated firm.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/lobbying-lobbyists.md
What lobbying_lobbyists does on Livedatalink
AI agents call lobbying_lobbyists 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 | number | — | Page number for pagination. |
page_size | number | — | Results per page (default 20). |
lobbyist_name | string | — | Lobbyist name, partial match. |
registrant_name | string | — | Optional registrant (firm) name to scope the search. |
Parameters from the server's own tool schema.
Why lobbying_lobbyists is rated Low
This tool retrieves and queries publicly available lobbying records without modification, deletion, or execution of code. It is a straightforward search operation that returns information about registered lobbyists and their firm associations. No side effects, reversible actions, or financial impact occur. This is a standard read/query operation against a public data source.
From the tool's definition Search individual lobbyists by name (and optionally by their registrant firm). Returns lobbyist records with their associated firm.
Attacks that exploit this kind of access
The rule that runs lobbying_lobbyists 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_lobbyists, this is the rule to start with:
lobbying_lobbyists 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_lobbyists call is checked against it from then on.
Questions about lobbying_lobbyists
Search individual lobbyists by name (and optionally by their registrant firm). Returns lobbyist records with their associated firm. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
lobbying_lobbyists accepts 4 parameters: page, page_size, 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_lobbyists: 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_lobbyists 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_lobbyists 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_lobbyists. 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_lobbyists 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