federalregister.documents.search
Search official US Federal Register documents (final rules, proposed rules, notices, presidential documents) by full-text term, agency, document type, and publication date range. Returns document number, title, abstract, type, agencies, and links. Data: federalregister.gov (GPO/NARA), no auth req...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/federalregister.documents.search.md
What federalregister.documents.search does on Apibase
AI agents call federalregister.documents.search to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | Page number for pagination (default 1). |
term | string | — | Full-text search term (e.g. "climate", "artificial intelligence"). |
type | string | — | Document type: RULE (final rule), PRORULE (proposed rule), NOTICE, or PRESDOCU (presidential document). |
order | string | — | Result ordering (default "newest"). |
per_page | integer | — | Results per page, 1-100 (default 20). |
agency_slug | string | — | Restrict results to one agency, by its slug (e.g. "environmental-protection-agency"). Look up slugs with federalregister.agencies. |
publication_date_gte | string | — | Only documents published on/after this date, format YYYY-MM-DD. |
publication_date_lte | string | — | Only documents published on/before this date, format YYYY-MM-DD. |
Parameters from the server's own tool schema.
Why federalregister.documents.search is rated Low
Tool queries public Federal Register data with no side effects, authentication, or capability to modify or execute.
From the tool's definition Search official US Federal Register documents, returns document number, title, abstract, type, agencies, and links.
Attacks that exploit this kind of access
The rule that runs federalregister.documents.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For federalregister.documents.search, this is the rule to start with:
federalregister.documents.search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every federalregister.documents.search call is checked against it from then on.
Questions about federalregister.documents.search
Search official US Federal Register documents (final rules, proposed rules, notices, presidential documents) by full-text term, agency, document type, and publication date range. Returns document number, title, abstract, type, agencies, and links. Data: federalregister.gov (GPO/NARA), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
federalregister.documents.search accepts 8 parameters: page, term, type, order, per_page, agency_slug, publication_date_gte, publication_date_lte. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for federalregister.documents.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 Apibase. Nothing to install.
federalregister.documents.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 federalregister.documents.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 federalregister.documents.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.
federalregister.documents.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue