congress.legislation.bill_details
Get full details for a specific US bill by Congress number, type (hr/s), and bill number. Returns title, all sponsors, co-sponsor count, action history, committee referrals, policy subjects. Source: Congress.gov.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/congress.legislation.bill-details.md
What congress.legislation.bill_details does on Apibase
AI agents call congress.legislation.bill_details to retrieve information from Apibase 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 |
|---|---|---|---|
type | string | Yes | Bill type: hr (House bill), s (Senate bill), hjres, sjres, etc. |
number | integer | Yes | Bill number (e.g. 1 for HR 1) |
congress | integer | Yes | Congress number (e.g. 119 for 2025-2026, 118 for 2023-2024) |
Parameters from the server's own tool schema.
Why congress.legislation.bill_details is rated Low
Retrieves publicly available legislative information with no side effects or data modification.
From the tool's definition Get full details for a specific US bill; returns title, sponsors, history, referrals
Attacks that exploit this kind of access
The rule that runs congress.legislation.bill_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For congress.legislation.bill_details, this is the rule to start with:
congress.legislation.bill_details 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 Apibase, apply this rule, and every congress.legislation.bill_details call is checked against it from then on.
Questions about congress.legislation.bill_details
Get full details for a specific US bill by Congress number, type (hr/s), and bill number. Returns title, all sponsors, co-sponsor count, action history, committee referrals, policy subjects. Source: Congress.gov. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
congress.legislation.bill_details accepts 3 parameters: type, number, congress. Required: type, number, congress. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for congress.legislation.bill_details: 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 Apibase. Nothing to install.
congress.legislation.bill_details 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.legislation.bill_details 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.legislation.bill_details. 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.legislation.bill_details is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue