fcc.regulatory.search_filings
Search FCC regulatory filings, public comments, and orders within ECFS proceedings. Returns filer names, law firms, submission types, document links, and dates. Use to find public comments on FCC rules, industry petitions, and official orders. Filter by docket number (e.g. "17-108" for Restoring ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/fcc.regulatory.search-filings.md
What fcc.regulatory.search_filings does on Apibase
AI agents call fcc.regulatory.search_filings 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 field and direction (e.g. "date_received,DESC" or "date_disseminated,ASC"). Default: newest received first. |
limit | integer | — | Number of filings to return (default 10, max 25). |
docket | string | — | FCC docket/proceeding number to filter filings by (e.g. "17-108", "22-461", "21-93"). |
Parameters from the server's own tool schema.
Why fcc.regulatory.search_filings is rated Low
Tool queries public FCC regulatory filings and returns metadata without modifying or executing operations.
From the tool's definition Search FCC filings, public comments, orders. Returns filer names, law firms, submission types, document links, dates.
Attacks that exploit this kind of access
The rule that runs fcc.regulatory.search_filings 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 fcc.regulatory.search_filings, this is the rule to start with:
fcc.regulatory.search_filings 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 fcc.regulatory.search_filings call is checked against it from then on.
Questions about fcc.regulatory.search_filings
Search FCC regulatory filings, public comments, and orders within ECFS proceedings. Returns filer names, law firms, submission types, document links, and dates. Use to find public comments on FCC rules, industry petitions, and official orders. Filter by docket number (e.g. "17-108" for Restoring Internet Freedom, "22-461" for broadband) or browse recent filings. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
fcc.regulatory.search_filings accepts 3 parameters: sort, limit, docket. 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 fcc.regulatory.search_filings: 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.
fcc.regulatory.search_filings 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 fcc.regulatory.search_filings 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 fcc.regulatory.search_filings. 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.
fcc.regulatory.search_filings 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