📚 GET ALL 40 GOVERNMENT DOCUMENT COLLECTIONS with counts. Essential starting point for targeted searches. Returns collection codes and names for: BILLS (285,173 congressional bills), USCOURTS (2.1M court opinions), CFR (6,577 packages with 7.7M granules), FR (22,687 Federal Register issues), CRE...
AI agents call collections 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 lists metadata about government document collections. It has no side effects, performs no modifications, and does not execute code or commands. It is a straightforward read operation returning static collection information for use as reference data in other queries.
From the tool's definition GET ALL 40 GOVERNMENT DOCUMENT COLLECTIONS with counts. Returns collection codes and names. The description uses only retrieval language: 'GET', 'Returns', 'search tools' (for filtering input). No modification, deletion, or execution mentioned.
Attacks that exploit this kind of access
📚 GET ALL 40 GOVERNMENT DOCUMENT COLLECTIONS with counts. Essential starting point for targeted searches. Returns collection codes and names for: BILLS (285,173 congressional bills), USCOURTS (2.1M court opinions), CFR (6,577 packages with 7.7M granules), FR (22,687 Federal Register issues), CREC (Congressional Record), PLAW (Public Laws), and 34 more collections. Use collection codes in other search tools for precise filtering. 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: 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 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 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. 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 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 →