legal.regulations.document
Get full details of a US federal regulatory document by ID — title, abstract, agency, comment count, docket, dates. Public domain (Regulations.gov)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/legal.regulations.document.md
What legal.regulations.document does on Apibase
AI agents call legal.regulations.document 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_id | string | Yes | Document ID from search results (e.g. "FDA-2024-N-0001-0001") |
Parameters from the server's own tool schema.
Why legal.regulations.document is rated Low
Retrieves publicly available regulatory document metadata without side effects or access restrictions.
From the tool's definition Get full details of US federal regulatory document by ID; public domain
Attacks that exploit this kind of access
The rule that runs legal.regulations.document 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 legal.regulations.document, this is the rule to start with:
legal.regulations.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 Apibase, apply this rule, and every legal.regulations.document call is checked against it from then on.
Questions about legal.regulations.document
Get full details of a US federal regulatory document by ID — title, abstract, agency, comment count, docket, dates. Public domain (Regulations.gov). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
legal.regulations.document accepts 1 parameter: document_id. Required: document_id. 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 legal.regulations.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 Apibase. Nothing to install.
legal.regulations.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 legal.regulations.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 legal.regulations.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.
legal.regulations.document 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