legal.regulations.search
Search US federal regulatory documents — rules, proposed rules, notices, presidential documents. Filter by agency (EPA, SEC, FDA...), document type, date. 7,500+ results for "artificial intelligence" (Regulations.gov)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/legal.regulations.search.md
What legal.regulations.search does on Apibase
AI agents call legal.regulations.search 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 |
|---|---|---|---|
sort | string | — | Sort order (default: -postedDate, newest first) |
limit | integer | — | Number of results (default 10, min 5, max 25) |
query | string | — | Search keywords in federal regulatory documents (e.g. "artificial intelligence", "climate change") |
agency | string | — | Filter by agency ID (e.g. "EPA", "SEC", "FDA") |
posted_after | string | — | Only documents posted after this date (YYYY-MM-DD) |
document_type | string | — | Filter by document type |
Parameters from the server's own tool schema.
Why legal.regulations.search is rated Low
Tool retrieves regulatory information without modifying, executing code, or creating financial obligations.
From the tool's definition Search US federal regulatory documents — rules, proposed rules, notices, presidential documents.
Attacks that exploit this kind of access
The rule that runs legal.regulations.search 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.search, this is the rule to start with:
legal.regulations.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 Apibase, apply this rule, and every legal.regulations.search call is checked against it from then on.
Questions about legal.regulations.search
Search US federal regulatory documents — rules, proposed rules, notices, presidential documents. Filter by agency (EPA, SEC, FDA...), document type, date. 7,500+ results for "artificial intelligence" (Regulations.gov). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
legal.regulations.search accepts 6 parameters: sort, limit, query, agency, posted_after, document_type. 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.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 Apibase. Nothing to install.
legal.regulations.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 legal.regulations.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 legal.regulations.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.
legal.regulations.search 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