lobbying_registrants
Search registered lobbying firms (registrants) by name. Returns registrant profile records.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/lobbying-registrants.md
What lobbying_registrants does on Livedatalink
AI agents call lobbying_registrants 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). |
registrant_name | string | — | Registrant (firm) name, partial match. |
Parameters from the server's own tool schema.
Why lobbying_registrants is rated Low
This tool performs a search and retrieval operation on lobbying registrant records, which is a Read category function. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. The blast radius of misuse is minimal—an agent could retrieve information about lobbying firms but cannot alter records or trigger external operations.
From the tool's definition Tool name 'lobbying_registrants' and description 'Search registered lobbying firms (registrants) by name. Returns registrant profile records.' indicate a read-only query operation that retrieves publicly available registrant data without modification or…
Attacks that exploit this kind of access
The rule that runs lobbying_registrants 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_registrants, this is the rule to start with:
lobbying_registrants 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_registrants call is checked against it from then on.
Questions about lobbying_registrants
Search registered lobbying firms (registrants) by name. Returns registrant profile records. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
lobbying_registrants accepts 2 parameters: page_size, 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_registrants: 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_registrants 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_registrants 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_registrants. 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_registrants 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