federalregister.documents.public_inspection
Get documents currently on public inspection at the Federal Register — filed but not yet officially published, available ahead of their scheduled publication date. Optionally filter by agency name. Data: federalregister.gov (GPO/NARA), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/federalregister.documents.public-inspection.md
What federalregister.documents.public_inspection does on Apibase
AI agents call federalregister.documents.public_inspection 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 |
|---|---|---|---|
max | integer | — | Maximum number of documents to return (1-100, default 20). |
agency | string | — | Filter by agency name substring, case-insensitive (e.g. "postal"). Omit to return all currently filed documents. |
Parameters from the server's own tool schema.
Why federalregister.documents.public_inspection is rated Low
Tool retrieves public inspection documents from Federal Register with no side effects or modifications.
From the tool's definition Get documents currently on public inspection, filed but not yet officially published
Attacks that exploit this kind of access
The rule that runs federalregister.documents.public_inspection 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.public_inspection, this is the rule to start with:
federalregister.documents.public_inspection 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.public_inspection call is checked against it from then on.
Questions about federalregister.documents.public_inspection
Get documents currently on public inspection at the Federal Register — filed but not yet officially published, available ahead of their scheduled publication date. Optionally filter by agency name. 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.public_inspection accepts 2 parameters: max, agency. 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.public_inspection: 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.public_inspection 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.public_inspection 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.public_inspection. 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.public_inspection 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