search_hearings
AI agents call search_hearings to retrieve information from Open Assembly without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries hearing information from legislative records with no side effects. It follows the same read-only pattern as other tools on this server which access bills, members, votes, and committees. The empty description lowers confidence slightly, but the naming and sibling context sufficiently establish this as a Read operation.
From the tool's definition Tool name 'search_hearings' indicates a search/query operation. The sibling tools (analyze_legislator, get_bill_detail, get_member_info, get_member_votes) are all retrieval operations, establishing the pattern that this server provides read-only access to…
Attacks that exploit this kind of access
search_hearings. It is categorised as a Read tool in the Open Assembly MCP Server, which means it retrieves data without modifying state.
Register the Open Assembly MCP server in PolicyLayer and add a rule for search_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 Open Assembly. Nothing to install.
search_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 search_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 search_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.
search_hearings is provided by the Open Assembly MCP server (kyusik-yang/open-assembly-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 →