🔍 POWERFUL FULL-TEXT SEARCH across 7.7+ million government documents. Search congressional bills, federal regulations, court opinions, presidential documents, and more. Returns document metadata with direct links to HTML, PDF, XML, and ZIP formats. Tested: 643,573 results for
AI agents call search 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 is a search/query tool that retrieves and returns publicly available government document metadata. It has no side effects, cannot modify data, execute code, or delete information. The capability is purely informational retrieval, making it a straightforward Read category with low severity.
From the tool's definition Tool performs 'FULL-TEXT SEARCH across 7.7+ million government documents' and 'Returns document metadata with direct links' — retrieval and query operations with no data modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
🔍 POWERFUL FULL-TEXT SEARCH across 7.7+ million government documents. Search congressional bills, federal regulations, court opinions, presidential documents, and more. Returns document metadata with direct links to HTML, PDF, XML, and ZIP formats. Tested: 643,573 results for. 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 search: 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.
search 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 search 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 search. 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.
search 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 →