congress_bill_actions
Get the chronological legislative action history for one bill (introductions, committee referrals, votes, becoming law). Requires Congress number, bill type, and bill number.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/congress-bill-actions.md
What congress_bill_actions does on Livedatalink
AI agents call congress_bill_actions 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 |
|---|---|---|---|
limit | number | — | Max actions (default 50). |
congress | number | Yes | Congress number. |
bill_type | string | Yes | Bill type code: hr (House Bill), s (Senate Bill), hjres, sjres, hconres, sconres, hres, sres. |
bill_number | number | Yes | Bill number. |
Parameters from the server's own tool schema.
Why congress_bill_actions is rated Low
This tool queries publicly available legislative data and returns information without side effects. It is purely informational (Get operation), making it a Read category tool with low severity since it cannot be misused to modify, destroy, or access restricted data.
From the tool's definition Tool retrieves 'chronological legislative action history for one bill' with no modification or deletion capabilities. Input parameters (Congress number, bill type, bill number) are identifiers only, not commands that alter state.
Attacks that exploit this kind of access
The rule that runs congress_bill_actions 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 congress_bill_actions, this is the rule to start with:
congress_bill_actions 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 congress_bill_actions call is checked against it from then on.
Questions about congress_bill_actions
Get the chronological legislative action history for one bill (introductions, committee referrals, votes, becoming law). Requires Congress number, bill type, and bill number. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
congress_bill_actions accepts 4 parameters: limit, congress, bill_type, bill_number. Required: congress, bill_type, bill_number. 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 congress_bill_actions: 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.
congress_bill_actions 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 congress_bill_actions 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 congress_bill_actions. 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.
congress_bill_actions 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