List the legislative sessions for a US state (regular and special), with start/end years and session IDs. Useful to scope which session to track bills in. Example: list_sessions({ state: "NY" })
AI agents call list_sessions to retrieve information from Legiscan without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
state | string | Yes | 2-letter state abbreviation, e.g. "NY", "FL", "CA". |
_apiKey | string | — | Optional — your own LegiScan API key for higher limits; omit to use the shared Pipeworx key. |
Parameters from the server's own tool schema.
This tool retrieves and queries legislative session metadata from the LegiScan API with no side effects. It neither creates, modifies, deletes, executes code, nor moves money. The action is purely informational lookup, fitting the Read category with low severity since exposing legislative session dates and IDs poses minimal risk.
From the tool's definition Tool name is 'list_sessions' and description states it 'List[s] the legislative sessions' with no modification or deletion capability. Returns metadata (start/end years, session IDs) for scoping purposes.
Attacks that exploit this kind of access
List the legislative sessions for a US state (regular and special), with start/end years and session IDs. Useful to scope which session to track bills in. Example: list_sessions({ state: "NY" }). It is categorised as a Read tool in the Legiscan MCP Server, which means it retrieves data without modifying state.
list_sessions accepts 2 parameters: state, _apiKey. Required: state. The full parameter table on this page comes from the server's own tool schema.
Register the Legiscan MCP server in PolicyLayer and add a rule for list_sessions: 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 Legiscan. Nothing to install.
list_sessions 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 list_sessions 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 list_sessions. 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.
list_sessions is provided by the Legiscan MCP server (pipeworx-io/mcp-legiscan). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →