nasa-cmr.datasets.detail
Retrieve full UMM (Universal Metadata Model) metadata for a specific NASA CMR collection identified by its concept ID (e.g. "C2515837343-GES_DISC"). Returns abstract, version, processing level, temporal extents, observing platforms and instruments, science keywords (GCMD taxonomy: category/topic/...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nasa-cmr.datasets.detail.md
What nasa-cmr.datasets.detail does on Apibase
AI agents call nasa-cmr.datasets.detail 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 |
|---|---|---|---|
concept_id | string | Yes | CMR concept ID of the collection to retrieve full UMM metadata for (e.g. "C2515837343-GES_DISC"). Obtain concept IDs from nasa-cmr.datasets.search results. |
Parameters from the server's own tool schema.
Why nasa-cmr.datasets.detail is rated Low
Retrieves public NASA dataset metadata with no side effects or data modifications.
From the tool's definition Retrieve full UMM metadata for specific NASA CMR collection. Returns abstract, version, processing level, temporal extents.
Attacks that exploit this kind of access
The rule that runs nasa-cmr.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 nasa-cmr.datasets.detail, this is the rule to start with:
nasa-cmr.datasets.detail 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 nasa-cmr.datasets.detail call is checked against it from then on.
Questions about nasa-cmr.datasets.detail
Retrieve full UMM (Universal Metadata Model) metadata for a specific NASA CMR collection identified by its concept ID (e.g. "C2515837343-GES_DISC"). Returns abstract, version, processing level, temporal extents, observing platforms and instruments, science keywords (GCMD taxonomy: category/topic/term), DOI, related URLs, and data center information. Concept IDs are obtained from nasa-cmr.datasets.search results. Essential for understanding dataset scope, instrument provenance, and citation details before downloading granules. Source: NASA CMR — US Gov public domain, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nasa-cmr.datasets.detail accepts 1 parameter: concept_id. Required: concept_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 nasa-cmr.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.
nasa-cmr.datasets.detail 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 nasa-cmr.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 nasa-cmr.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.
nasa-cmr.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