reg_document
Get full metadata and a plain-text body excerpt for a single Federal Register document by its document number (e.g. '2026-09905'). Returns title, type, agencies, abstract, affected CFR parts, a leading excerpt of the full rule text, and the URL for the complete document.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/reg-document.md
What reg_document does on Livedatalink
AI agents call reg_document to retrieve information from Livedatalink 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-09905'. |
Parameters from the server's own tool schema.
Why reg_document is rated Low
This is a read-only retrieval operation that queries and returns information about public Federal Register documents. It has no side effects, cannot modify data, and poses minimal risk even if an AI agent calls it with arbitrary document numbers—it simply returns publicly available regulatory information.
From the tool's definition Tool retrieves 'full metadata and a plain-text body excerpt for a single Federal Register document' by document number. Operations are: get title, type, agencies, abstract, CFR parts, excerpt, and URL.
Attacks that exploit this kind of access
The rule that runs reg_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reg_document, this is the rule to start with:
reg_document 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 Livedatalink, apply this rule, and every reg_document call is checked against it from then on.
Questions about reg_document
Get full metadata and a plain-text body excerpt for a single Federal Register document by its document number (e.g. '2026-09905'). Returns title, type, agencies, abstract, affected CFR parts, a leading excerpt of the full rule text, and the URL for the complete document. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
reg_document 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 Livedatalink MCP server in PolicyLayer and add a rule for reg_document: 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 Livedatalink. Nothing to install.
reg_document 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 reg_document 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 reg_document. 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.
reg_document is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue