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

openstates.legislature.committees

List legislative committees for a US state, optionally filtered by chamber (upper/lower) or type (committee/subcommittee). Returns committee name, chamber, jurisdiction, and parent committee for subcommittees. Useful for identifying which committee oversees a policy area or finding where a bill i...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 50 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.committees.md

What openstates.legislature.committees does on Apibase

AI agents call openstates.legislature.committees 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
page integer — Page number for pagination (default 1).
chamber string — Filter by chamber (e.g. "upper" for Senate, "lower" for House/Assembly, "legislature" for joint committees).
per_page integer — Number of results per page (1–50, default 20).
jurisdiction string — State or jurisdiction abbreviation to list committees for (e.g. "ca", "tx", "ny").
classification string — Filter by committee classification (e.g. "committee", "subcommittee").

Parameters from the server's own tool schema.

Why openstates.legislature.committees is rated Low

Tool retrieves public legislative committee metadata without modification or execution capabilities.

From the tool's definition List legislative committees, identifies committee oversees, finding where bill assigned

Questions about openstates.legislature.committees

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

List legislative committees for a US state, optionally filtered by chamber (upper/lower) or type (committee/subcommittee). Returns committee name, chamber, jurisdiction, and parent committee for subcommittees. Useful for identifying which committee oversees a policy area or finding where a bill is assigned. Use jurisdiction codes such as "ca", "tx", "ny". 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.committees accept? +

openstates.legislature.committees accepts 5 parameters: page, chamber, per_page, jurisdiction, classification. The full parameter table on this page comes from the server's own tool schema.

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

Register the Apibase MCP server in PolicyLayer and add a rule for openstates.legislature.committees: 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.committees? +

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

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

Yes. Add a rate_limit block to the openstates.legislature.committees 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.committees completely? +

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

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

Across the catalogue

// 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.