đź“… GET RECENTLY PUBLISHED DOCUMENTS from specific date forward. Track new government publications in real-time. Tested: 130 bills published since 2026-03-20, including latest bills from current congress (119). Filter by collection (BILLS, FR, CFR, etc.) with pagination. Perfect for monitoring new...
AI agents call published 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 retrieves and queries government publication data with filtering options. It is purely informational with no side effects—no data is created, modified, deleted, or executed. The retrieval of historical government documents (bills, Federal Register notices, etc.) is a standard read operation with minimal risk of misuse.
From the tool's definition Tool description explicitly states 'GET RECENTLY PUBLISHED DOCUMENTS' and 'Track new government publications' with filtering and pagination capabilities. No modification, deletion, execution, or financial operations are performed.
Attacks that exploit this kind of access
đź“… GET RECENTLY PUBLISHED DOCUMENTS from specific date forward. Track new government publications in real-time. Tested: 130 bills published since 2026-03-20, including latest bills from current congress (119). Filter by collection (BILLS, FR, CFR, etc.) with pagination. Perfect for monitoring new legislation, Federal Register notices, court decisions, or any government document type. 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 published: 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.
published 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 published 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 published. 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.
published 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 →