federalregister.agencies.search
Search or list US federal government agencies tracked by the Federal Register (name, short name, slug, parent agency). Use the returned slug to filter federalregister.search by agency. Data: federalregister.gov (GPO/NARA), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/federalregister.agencies.search.md
What federalregister.agencies.search does on Apibase
AI agents call federalregister.agencies.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 |
|---|---|---|---|
max | integer | — | Maximum number of agencies to return (1-50, default 20). |
query | string | — | Filter agencies by name substring, case-insensitive (e.g. "environmental"). Omit to list top agencies. |
Parameters from the server's own tool schema.
Why federalregister.agencies.search is rated Low
Retrieves publicly available agency metadata with no side effects or data modification.
From the tool's definition Search or list US federal government agencies tracked by the Federal Register
Attacks that exploit this kind of access
The rule that runs federalregister.agencies.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 federalregister.agencies.search, this is the rule to start with:
federalregister.agencies.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 federalregister.agencies.search call is checked against it from then on.
Questions about federalregister.agencies.search
Search or list US federal government agencies tracked by the Federal Register (name, short name, slug, parent agency). Use the returned slug to filter federalregister.search by agency. Data: federalregister.gov (GPO/NARA), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
federalregister.agencies.search accepts 2 parameters: max, query. 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 federalregister.agencies.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.
federalregister.agencies.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 federalregister.agencies.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 federalregister.agencies.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.
federalregister.agencies.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