get_bill_history
AI agents call get_bill_history 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.
The tool name and pattern of sibling read-only tools strongly indicate this retrieves historical information about bills (voting history, passage timeline, etc.) without modifying data. Empty description prevents perfect certainty, but context from 'Umbrella Terminal MCP' offering query/analysis of legislative data supports Read classification. No destructive, financial, or code-execution capabilities evident.
From the tool's definition Tool name 'get_bill_history' with empty description; sibling tools (get_bill, get_bill_amendments, get_bill_funding, get_bill_hearings, get_bill_lobby_positions) all perform read-only queries on legislative data.
Attacks that exploit this kind of access
get_bill_history. 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_bill_history: 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_bill_history 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_bill_history 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_bill_history. 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_bill_history 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 →