📊 FIND DOCUMENTS MODIFIED IN DATE RANGE within specific collections. Excellent for analyzing legislative activity periods or document update patterns. Tested: 221 bills modified between 2026-03-20 and 2026-03-25. Same advanced filtering as collections_search_last_modified. Ideal for tracking con...
AI agents call collections_search_last_modified_to_end_date 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 queries and retrieves government documents based on modification date filters. It has no side effects, does not create/modify/delete data, and does not execute external operations. It is a pure Read operation against a public government API.
From the tool's definition Tool performs document search and filtering within a date range ('FIND DOCUMENTS MODIFIED IN DATE RANGE') and is explicitly described as for 'analyzing', 'tracking', and 'testing' legislative activity.
Attacks that exploit this kind of access
📊 FIND DOCUMENTS MODIFIED IN DATE RANGE within specific collections. Excellent for analyzing legislative activity periods or document update patterns. Tested: 221 bills modified between 2026-03-20 and 2026-03-25. Same advanced filtering as collections_search_last_modified. Ideal for tracking congressional sessions, regulatory updates, or court opinion releases within specific timeframes. 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_to_end_date: 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_to_end_date 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_to_end_date 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_to_end_date. 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_to_end_date 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 →