get_representatives
Look up elected representatives for a given U.S. address, including federal, state, and local officials.
This record as markdown: /tools/com-govbase-govbase/get-representatives.md
What get_representatives does on Govbase
AI agents call get_representatives 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 | Street address (e.g., "1600 Pennsylvania Ave, Washington DC") |
Parameters from the server's own tool schema.
Why get_representatives is rated Low
This tool queries and returns publicly available civic information (elected representatives) based on an input address. It performs a lookup operation with no ability to modify data, execute commands, or cause irreversible changes. The data returned is public record information about government officials. This is a straightforward Read operation with minimal risk even if misused by an AI agent.
From the tool's definition 'Look up elected representatives for a given U.S. address' — retrieves public information about officials without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_representatives 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_representatives, this is the rule to start with:
get_representatives 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_representatives call is checked against it from then on.
Questions about get_representatives
Look up elected representatives for a given U.S. address, including federal, state, and local officials. It is categorised as a Read tool in the Govbase MCP Server, which means it retrieves data without modifying state.
get_representatives 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_representatives: 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_representatives 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_representatives 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_representatives. 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_representatives 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