reg_search
Search the Federal Register (the daily journal of the US government) for rules, proposed rules, notices, and presidential documents by keyword, with optional agency, document type, and publication-date filters. Returns each document's number, title, type, publishing agency, abstract, and URL. Use...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/reg-search.md
What reg_search does on Livedatalink
AI agents call reg_search 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 |
|---|---|---|---|
term | string | — | Keyword(s), e.g. 'methane emissions', 'overtime rule'. |
type | string | — | Optional document type: 'rule', 'proposed-rule', 'notice', or 'presidential-document'. |
limit | number | — | Max rows (default 20, max 100). |
agency | string | — | Optional agency slug, e.g. 'environmental-protection-agency', 'securities-and-exchange-commission'. |
published_to | string | — | Published on/before, ISO date yyyy-mm-dd. |
published_from | string | — | Published on/after, ISO date yyyy-mm-dd. |
Parameters from the server's own tool schema.
Why reg_search is rated Low
This tool retrieves publicly available government documents and metadata from the Federal Register. It has no side effects—it only queries and returns information. The severity is low because the Federal Register is public data with no sensitive access controls, and misuse by an AI agent would result only in information gathering, not data modification, deletion, or any actionable harm.
From the tool's definition Tool description states it 'Search[es] the Federal Register... for rules, proposed rules, notices, and presidential documents by keyword' and 'Returns each document's number, title, type, publishing agency, abstract, and URL.' These are all retrieval…
Attacks that exploit this kind of access
The rule that runs reg_search 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_search, this is the rule to start with:
reg_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 Livedatalink, apply this rule, and every reg_search call is checked against it from then on.
Questions about reg_search
Search the Federal Register (the daily journal of the US government) for rules, proposed rules, notices, and presidential documents by keyword, with optional agency, document type, and publication-date filters. Returns each document's number, title, type, publishing agency, abstract, and URL. Use reg_document to get the full text of one document. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
reg_search accepts 6 parameters: term, type, limit, agency, published_to, published_from. 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_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 Livedatalink. Nothing to install.
reg_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 reg_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 reg_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.
reg_search 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