federalregister.documents.detail
Get full detail for a single Federal Register document by its document number — abstract, action, agencies, CFR references, docket IDs, effective date, comment deadline, citation, and links to HTML/PDF/XML full text. Data: federalregister.gov (GPO/NARA), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/federalregister.documents.detail.md
What federalregister.documents.detail does on Apibase
AI agents call federalregister.documents.detail 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 |
|---|---|---|---|
document_number | string | Yes | Federal Register document number, e.g. "2026-17477". Obtained from federalregister.search results. |
Parameters from the server's own tool schema.
Why federalregister.documents.detail is rated Low
Retrieves public Federal Register document metadata and links; no side effects or data modification.
From the tool's definition Get full detail for a single Federal Register document, no auth required
Attacks that exploit this kind of access
The rule that runs federalregister.documents.detail 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.detail, this is the rule to start with:
federalregister.documents.detail 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.detail call is checked against it from then on.
Questions about federalregister.documents.detail
Get full detail for a single Federal Register document by its document number — abstract, action, agencies, CFR references, docket IDs, effective date, comment deadline, citation, and links to HTML/PDF/XML full text. 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.detail accepts 1 parameter: document_number. Required: document_number. 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.detail: 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.detail 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.detail 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.detail. 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.detail 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