New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

openstates.legislature.bill_detail

Get full details for a specific US state bill by jurisdiction, session, and bill identifier. Returns complete legislative history including all actions (committee referrals, readings, amendments, final votes), sponsor information, abstract/summary, and roll-call vote counts. Obtain jurisdiction a...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 33 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/openstates.legislature.bill-detail.md

What openstates.legislature.bill_detail does on Apibase

AI agents call openstates.legislature.bill_detail 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.

ParameterTypeRequiredDescription
bill_id string Yes Bill identifier within the session (e.g. "SB 700", "HB 1234", "SR 5"). Obtain from bills_search results.
session string Yes Legislative session identifier the bill belongs to (e.g. "20252026", "2024"). Obtain from bills_search results.
jurisdiction string Yes State abbreviation where the bill was introduced (e.g. "ca" for California, "ny" for New York).

Parameters from the server's own tool schema.

Why openstates.legislature.bill_detail is rated Low

Tool retrieves publicly available legislative bill information without side effects or data modification.

From the tool's definition Get full details, returns complete legislative history, obtain jurisdiction and session

Questions about openstates.legislature.bill_detail

What does the openstates.legislature.bill_detail tool do? +

Get full details for a specific US state bill by jurisdiction, session, and bill identifier. Returns complete legislative history including all actions (committee referrals, readings, amendments, final votes), sponsor information, abstract/summary, and roll-call vote counts. Obtain jurisdiction and session from bills_search results. Example: jurisdiction="ca", session="20252026", bill_id="SB 700". It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does openstates.legislature.bill_detail accept? +

openstates.legislature.bill_detail accepts 3 parameters: bill_id, session, jurisdiction. Required: bill_id, session, jurisdiction. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on openstates.legislature.bill_detail? +

Register the Apibase MCP server in PolicyLayer and add a rule for openstates.legislature.bill_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 Apibase. Nothing to install.

What risk level is openstates.legislature.bill_detail? +

openstates.legislature.bill_detail is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit openstates.legislature.bill_detail? +

Yes. Add a rate_limit block to the openstates.legislature.bill_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.

How do I block openstates.legislature.bill_detail completely? +

Set action: deny in the PolicyLayer policy for openstates.legislature.bill_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.

What MCP server provides openstates.legislature.bill_detail? +

openstates.legislature.bill_detail 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.