AI agents call gov.bill-summaries 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.
This is a data retrieval tool that queries publicly available legislative information. It has no side effects, does not modify data, execute code, delete records, or involve financial transactions. The query-and-filter capability is characteristic of a Read category tool. Severity is low because the data source (Congress.gov) is public and the tool only retrieves information without the ability to alter it.
From the tool's definition Tool retrieves 'latest US Congressional bill summaries' from Congress.gov with filtering options (congress, bill type, date range). No modification, deletion, or execution capability described.
Attacks that exploit this kind of access
Latest US Congressional bill summaries (CRS-authored, attached to specific bill versions) via Congress.gov. Filter by congress + bill type + 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.bill-summaries: 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.bill-summaries 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.bill-summaries 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.bill-summaries. 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.bill-summaries 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 →