get_district_legislators
AI agents call get_district_legislators to retrieve information from Umbrella Terminal MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves legislator data associated with a district—a read-only query operation with no side effects. It fits the Read category profile (search, list, get, fetch). No data is created, modified, deleted, or executed. The blast radius of misuse is minimal: an agent could request excessive legislator information but cannot cause harm through this tool alone.
From the tool's definition Tool name 'get_district_legislators' and server context indicate data retrieval. Sibling tools (get_bill, get_bill_amendments, get_bill_history, get_bill_hearings) are all Read operations.
Attacks that exploit this kind of access
get_district_legislators. It is categorised as a Read tool in the Umbrella Terminal MCP MCP Server, which means it retrieves data without modifying state.
Register the Umbrella Terminal MCP server in PolicyLayer and add a rule for get_district_legislators: 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 Umbrella Terminal MCP. Nothing to install.
get_district_legislators 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_district_legislators 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_district_legislators. 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_district_legislators is provided by the Umbrella Terminal MCP server (theblackcompany/umbrella_terminal_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 →