reg_cfr_search
Full-text search the current Code of Federal Regulations (eCFR, all 50 titles) for a phrase or keywords. Returns matching sections with their citation (e.g. '40 CFR 98.411'), hierarchy heading, a text snippet, effective date, and the official eCFR URL, plus the total match count. Use reg_cfr_sect...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/reg-cfr-search.md
What reg_cfr_search does on Livedatalink
AI agents call reg_cfr_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 |
|---|---|---|---|
limit | number | — | Max sections to return (default 20, max 100). |
query | string | Yes | Phrase or keywords to find in the CFR, e.g. 'greenhouse gas reporting'. |
Parameters from the server's own tool schema.
Why reg_cfr_search is rated Low
This is a query and retrieval operation against a public regulatory database. It retrieves information without side effects, making it a Read category tool. The severity is low because searching public regulatory text poses minimal risk even if misused by an AI agent—it cannot modify regulations, execute code, or affect external systems.
From the tool's definition Tool description explicitly states it performs 'Full-text search' and 'Returns matching sections' with citation and snippets. No modification, deletion, or execution capabilities are described. The tool reads/queries the Code of Federal Regulations database.
Attacks that exploit this kind of access
The rule that runs reg_cfr_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_cfr_search, this is the rule to start with:
reg_cfr_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_cfr_search call is checked against it from then on.
Questions about reg_cfr_search
Full-text search the current Code of Federal Regulations (eCFR, all 50 titles) for a phrase or keywords. Returns matching sections with their citation (e.g. '40 CFR 98.411'), hierarchy heading, a text snippet, effective date, and the official eCFR URL, plus the total match count. Use reg_cfr_section to read a full section's text. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
reg_cfr_search accepts 2 parameters: limit, query. Required: query. 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_cfr_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_cfr_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_cfr_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_cfr_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_cfr_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