Find a legislator
AI agents call legiscan_find_legislator to retrieve information from LegiScan MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available legislator information without side effects or ability to modify, delete, or execute operations. It is a pure read operation on legislative data, consistent with other sibling tools like legiscan_search, legiscan_get_person, and legiscan_get_legislator_votes.
From the tool's definition Tool name 'legiscan_find_legislator' and description 'Find a legislator' indicate a search/lookup operation. Server context confirms it retrieves legislative data (bills, votes, legislators, sessions) with no modification capability.
Attacks that exploit this kind of access
Find a legislator. It is categorised as a Read tool in the LegiScan MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LegiScan MCP Server MCP server in PolicyLayer and add a rule for legiscan_find_legislator: 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 MCP Server. Nothing to install.
legiscan_find_legislator 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 legiscan_find_legislator 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 legiscan_find_legislator. 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.
legiscan_find_legislator is provided by the LegiScan MCP Server MCP server (sh-patterson/legiscan-mcp). 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 →