get_committee_hearings
AI agents call get_committee_hearings 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 legislative hearing information about committees—a read-only operation with no side effects, data modification, or execution of external operations. Committee hearing records are typically public legislative data. The low severity reflects minimal risk even if misused, as the output is informational only.
From the tool's definition Tool name 'get_committee_hearings' indicates retrieval/query of public legislative hearing data; sibling tools like 'get_bill', 'get_bill_hearings', 'get_bill_history' confirm this server's design pattern is querying legislative intelligence without…
Attacks that exploit this kind of access
get_committee_hearings. 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_committee_hearings: 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_committee_hearings 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_committee_hearings 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_committee_hearings. 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_committee_hearings 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 →