get_voter_info
Get election and polling location information for a registered U.S. voter address, including upcoming elections and early vote sites.
This record as markdown: /tools/com-govbase-govbase/get-voter-info.md
What get_voter_info does on Govbase
AI agents call get_voter_info 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 |
|---|---|---|---|
address | string | Yes | Registered voter address |
Parameters from the server's own tool schema.
Why get_voter_info is rated Low
This tool retrieves publicly available or registry-based election and polling location data for a given voter address. While it accesses personal information (voter registration), it performs no side effects, does not modify or delete data, and does not execute external operations or commit financial transactions. It is clearly a Read operation.
From the tool's definition Tool name 'get_voter_info' and description 'Get election and polling location information' — the verb 'Get' and the qualifier 'election and polling location information' indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs get_voter_info 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_voter_info, this is the rule to start with:
get_voter_info 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_voter_info call is checked against it from then on.
Questions about get_voter_info
Get election and polling location information for a registered U.S. voter address, including upcoming elections and early vote sites. It is categorised as a Read tool in the Govbase MCP Server, which means it retrieves data without modifying state.
get_voter_info accepts 1 parameter: address. Required: address. 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_voter_info: 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_voter_info 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_voter_info 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_voter_info. 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_voter_info 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