📊 GET PUBLICATIONS IN SPECIFIC DATE RANGE for analyzing publication patterns and legislative activity periods. Tested: 66 bills published between 2026-03-25 and 2026-03-29, including latest International Transgender Day of Visibility resolution (2026-03-27). Excellent for tracking congressional ...
AI agents call published_end 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 only retrieves and queries publicly available government publication data based on date filters. It has no side effects, cannot modify data, execute code, or perform financial transactions. The low severity reflects that misuse would simply return unwanted data subsets with no harmful consequences.
From the tool's definition Tool name 'published_end' and description state it retrieves publications in a specific date range for 'analyzing publication patterns' and 'tracking congressional session activity'.
Attacks that exploit this kind of access
📊 GET PUBLICATIONS IN SPECIFIC DATE RANGE for analyzing publication patterns and legislative activity periods. Tested: 66 bills published between 2026-03-25 and 2026-03-29, including latest International Transgender Day of Visibility resolution (2026-03-27). Excellent for tracking congressional session activity, regulatory publication periods, or court decision 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 published_end: 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_end 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_end 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_end. 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_end 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 →