hf.hub.datasets
Search 200K+ datasets on HuggingFace Hub by name or keyword. Returns dataset ID, downloads, likes, tags. Covers NLP, vision, audio, tabular datasets. Sorted by downloads.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hf.hub.datasets.md
What hf.hub.datasets does on Apibase
AI agents call hf.hub.datasets 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 |
|---|---|---|---|
limit | integer | — | Number of results (1-20, default 10) |
search | string | Yes | Search query — dataset name or keyword (e.g. "wikipedia", "imagenet", "squad") |
Parameters from the server's own tool schema.
Why hf.hub.datasets is rated Low
Queries public dataset metadata with no side effects or modification capability.
From the tool's definition Search datasets, returns dataset ID, downloads, likes, tags.
Attacks that exploit this kind of access
The rule that runs hf.hub.datasets 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 hf.hub.datasets, this is the rule to start with:
hf.hub.datasets 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 hf.hub.datasets call is checked against it from then on.
Questions about hf.hub.datasets
Search 200K+ datasets on HuggingFace Hub by name or keyword. Returns dataset ID, downloads, likes, tags. Covers NLP, vision, audio, tabular datasets. Sorted by downloads. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
hf.hub.datasets accepts 2 parameters: limit, search. Required: search. 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 hf.hub.datasets: 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.
hf.hub.datasets 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 hf.hub.datasets 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 hf.hub.datasets. 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.
hf.hub.datasets 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