📅 FIND RECENTLY MODIFIED DOCUMENTS in specific collections since a given date. Perfect for tracking legislative updates and document changes. Tested: 245 bills modified since 2026-03-25. Supports advanced filtering by congress (119 for current), docClass (hr/s for bills), billVersion, courtCode/...
AI agents call collections_search_last_modified to retrieve information from Gov info api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only queries against government document collections with temporal and categorical filters. It retrieves information without side effects or state changes. The supported operations (filtering by congress, docClass, state, topic, etc.) are all retrieval operations typical of a search/query API.
From the tool's definition Tool description states 'FIND RECENTLY MODIFIED DOCUMENTS' and 'tracking legislative updates and document changes' — it searches/queries government documents by modification date with filtering parameters.
Attacks that exploit this kind of access
📅 FIND RECENTLY MODIFIED DOCUMENTS in specific collections since a given date. Perfect for tracking legislative updates and document changes. Tested: 245 bills modified since 2026-03-25. Supports advanced filtering by congress (119 for current), docClass (hr/s for bills), billVersion, courtCode/Type, state, topic, and more. Use with BILLS, CFR, FR, or any collection code from the collections tool. It is categorised as a Read tool in the Gov info api MCP Server, which means it retrieves data without modifying state.
Register the Gov info api MCP server in PolicyLayer and add a rule for collections_search_last_modified: 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 Gov info api. Nothing to install.
collections_search_last_modified 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 collections_search_last_modified 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 collections_search_last_modified. 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.
collections_search_last_modified is provided by the Gov info api MCP server (n00dlefr34k/gov-info-api-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 →