hdx.datasets.detail
Get full metadata for a single HDX dataset by id or URL slug: description, publishing organization, covered locations, tags, update frequency, license, source, and the full list of downloadable resources (name, format, download URL, size). Use hdx.dataset_search first to find a dataset id. Data: ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hdx.datasets.detail.md
What hdx.datasets.detail does on Apibase
AI agents use hdx.datasets.detail to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | HDX dataset id or URL slug (e.g. "hdx-hapi-som") |
Parameters from the server's own tool schema.
Why hdx.datasets.detail is rated Medium
An AI agent can call hdx.datasets.detail faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs hdx.datasets.detail 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 hdx.datasets.detail, this is the rule to start with:
hdx.datasets.detail stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 hdx.datasets.detail call is checked against it from then on.
Questions about hdx.datasets.detail
Get full metadata for a single HDX dataset by id or URL slug: description, publishing organization, covered locations, tags, update frequency, license, source, and the full list of downloadable resources (name, format, download URL, size). Use hdx.dataset_search first to find a dataset id. Data: HDX CKAN Action API (data.humdata.org), no auth required. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
hdx.datasets.detail accepts 1 parameter: id. Required: id. 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 hdx.datasets.detail: 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.
hdx.datasets.detail is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the hdx.datasets.detail 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 hdx.datasets.detail. 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.
hdx.datasets.detail 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