congress.legislation.bills
Search US federal bills and resolutions from 1973 to present. Filter by Congress number (93-119), bill type (hr/s/hjres/sjres). Returns title, sponsor, party, latest action, policy area. Source: Congress.gov (Library of Congress).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/congress.legislation.bills.md
What congress.legislation.bills does on Apibase
AI agents call congress.legislation.bills 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 | — | Bill type: hr (House), s (Senate), hjres, sjres, hconres, sconres, hres, sres |
limit | integer | — | Number of results (1-25, default 10) |
congress | integer | — | Congress number (93=1973 to 119=2025-2026). Default: current (119). |
Parameters from the server's own tool schema.
Why congress.legislation.bills is rated Low
Tool retrieves legislative data with no side effects or data modification capabilities.
From the tool's definition Search US federal bills and resolutions, returns title, sponsor, party, latest action
Attacks that exploit this kind of access
The rule that runs congress.legislation.bills 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.bills, this is the rule to start with:
congress.legislation.bills 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.bills call is checked against it from then on.
Questions about congress.legislation.bills
Search US federal bills and resolutions from 1973 to present. Filter by Congress number (93-119), bill type (hr/s/hjres/sjres). Returns title, sponsor, party, latest action, policy area. Source: Congress.gov (Library of Congress). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
congress.legislation.bills accepts 3 parameters: type, limit, 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.bills: 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.bills 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.bills 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.bills. 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.bills 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