get_member_vote
Check how a specific U.S. member of Congress voted on a policy by providing their Bioguide ID and the policy ID. Returns all roll call votes for that member on the given policy.
This record as markdown: /tools/com-govbase-govbase/get-member-vote.md
What get_member_vote does on Govbase
AI agents call get_member_vote to retrieve information from Govbase 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 |
|---|---|---|---|
policy_id | string | Yes | Policy ID to check vote on |
bioguide_id | string | Yes | Bioguide ID of the member |
Parameters from the server's own tool schema.
Why get_member_vote is rated Low
This tool queries and retrieves historical voting records from a public civic data repository. It performs a lookup operation with no side effects—it neither modifies voting data, executes code, nor triggers external actions. The data returned (congressional voting records) is publicly available information. This is a straightforward Read operation.
From the tool's definition Tool name 'get_member_vote' and description 'Check how a specific U.S. member of Congress voted on a policy' and 'Returns all roll call votes' indicate data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs get_member_vote safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Govbase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_member_vote, this is the rule to start with:
get_member_vote 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 Govbase, apply this rule, and every get_member_vote call is checked against it from then on.
Questions about get_member_vote
Check how a specific U.S. member of Congress voted on a policy by providing their Bioguide ID and the policy ID. Returns all roll call votes for that member on the given policy. It is categorised as a Read tool in the Govbase MCP Server, which means it retrieves data without modifying state.
get_member_vote accepts 2 parameters: policy_id, bioguide_id. Required: policy_id, bioguide_id. The full parameter table on this page comes from the server's own tool schema.
Register the Govbase MCP server in PolicyLayer and add a rule for get_member_vote: 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 Govbase. Nothing to install.
get_member_vote 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 get_member_vote 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 get_member_vote. 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.
get_member_vote is provided by the Govbase MCP server (https://api.govbase.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Govbase, and thousands of servers like it.
This server
Across the catalogue