lobbying_detail
Get the full detail of one lobbying filing by its UUID (from lobbying_search results), including all lobbying activities, issues, covered officials contacted, and the lobbyists involved.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/lobbying-detail.md
What lobbying_detail does on Livedatalink
AI agents call lobbying_detail 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 |
|---|---|---|---|
filing_uuid | string | Yes | Filing UUID from lobbying_search results. |
Parameters from the server's own tool schema.
Why lobbying_detail is rated Low
This tool queries and returns publicly available lobbying disclosure information. It retrieves data (lobbying filing details) without modifying, deleting, or executing any operations. The data returned appears to be from public government disclosure records. No destructive, financial, or execution capabilities are present. This is a standard data retrieval operation with minimal risk.
From the tool's definition Tool retrieves 'full detail of one lobbying filing' by UUID, returning information about 'lobbying activities, issues, covered officials contacted, and the lobbyists involved.' The verb 'Get' and the retrieving of existing filing data indicates a read…
Attacks that exploit this kind of access
The rule that runs lobbying_detail 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_detail, this is the rule to start with:
lobbying_detail 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_detail call is checked against it from then on.
Questions about lobbying_detail
Get the full detail of one lobbying filing by its UUID (from lobbying_search results), including all lobbying activities, issues, covered officials contacted, and the lobbyists involved. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
lobbying_detail accepts 1 parameter: filing_uuid. Required: filing_uuid. 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_detail: 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_detail 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_detail 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_detail. 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_detail 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