AI agents call gov.congress-hearing to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves publicly available Congressional hearing data from Congress.gov. It supports querying by congress, chamber, and jacket number, or listing by congress and chamber with optional date filtering. All operations are read-only queries that retrieve information without creating, modifying, deleting, or executing any side effects.
From the tool's definition Tool description states 'US Congressional hearings (Congress.gov)' with operations to 'Pass congress+chamber+jacketNumber for single hearing; otherwise list by congress+chamber with optional date range.' These are query/retrieval operations with no…
Attacks that exploit this kind of access
US Congressional hearings (Congress.gov). Pass congress+chamber+jacketNumber for single hearing; otherwise list by congress+chamber with optional date range. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for gov.congress-hearing: 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 Mcp. Nothing to install.
gov.congress-hearing 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 gov.congress-hearing 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 gov.congress-hearing. 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.
gov.congress-hearing is provided by the MCP server (@2sio/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 →