📋 GET COMPLETE PACKAGE METADATA including sponsors, committees, bill status, and download links. Returns comprehensive details like title, congress, chamber, bill type, members (sponsors/cosponsors with party/state), committees assigned, and direct links to HTML, PDF, XML, ZIP formats. Tested wi...
AI agents call package_summary 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 legislative data, retrieving and presenting existing information without side effects, data modification, code execution, or destructive actions. The explicit mention of 'GET' and 'returns' confirms retrieval semantics with no capability to alter state.
From the tool's definition Tool retrieves and returns metadata only: 'GET COMPLETE PACKAGE METADATA including sponsors, committees, bill status, and download links' with results like 'title, congress, chamber, bill type, members, committees assigned, and direct links'.
Attacks that exploit this kind of access
📋 GET COMPLETE PACKAGE METADATA including sponsors, committees, bill status, and download links. Returns comprehensive details like title, congress, chamber, bill type, members (sponsors/cosponsors with party/state), committees assigned, and direct links to HTML, PDF, XML, ZIP formats. Tested with Border Security Investment Act (HR 445) showing 7 sponsors, 2 committees, 8 pages. Essential for detailed bill analysis. 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 package_summary: 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.
package_summary 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 package_summary 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 package_summary. 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.
package_summary 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 →