gribstream_list_datasets
NO AUTH / PUBLIC / READ-ONLY. Lists public GribStream datasets and metadata. This tool does not query weather values and cannot return forecast data. Supports catalog filters such as code, family, tag, and is_ensemble.
This record as markdown: /tools/com-gribstream-mcp/gribstream-list-datasets.md
What gribstream_list_datasets does on GribStream MCP
AI agents call gribstream_list_datasets to retrieve information from GribStream MCP 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 |
|---|---|---|---|
tag | object | — | Tag or list of tags. Multiple tags use AND semantics in the API. |
code | object | — | Dataset code or list of dataset codes, for example gfs or ["gfs", "ifsoper"]. |
family | string | — | Dataset family filter, for example gfs, ifs, nbm, hrrr, rap, rtma, urma. |
is_ensemble | boolean | — | Filter to ensemble datasets when true, or deterministic datasets when false. |
Parameters from the server's own tool schema.
Why gribstream_list_datasets is rated Low
This tool retrieves and lists dataset metadata without executing queries, modifying data, or triggering external operations. It is a straightforward read operation on public data with minimal blast radius if misused by an AI agent—the worst case being unnecessary API calls or catalog exploration. No irreversible actions, code execution, or data modification is possible.
From the tool's definition Tool description explicitly states 'NO AUTH / PUBLIC / READ-ONLY' and 'Lists public GribStream datasets and metadata.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs gribstream_list_datasets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GribStream MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gribstream_list_datasets, this is the rule to start with:
gribstream_list_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 GribStream MCP, apply this rule, and every gribstream_list_datasets call is checked against it from then on.
Questions about gribstream_list_datasets
NO AUTH / PUBLIC / READ-ONLY. Lists public GribStream datasets and metadata. This tool does not query weather values and cannot return forecast data. Supports catalog filters such as code, family, tag, and is_ensemble. It is categorised as a Read tool in the GribStream MCP MCP Server, which means it retrieves data without modifying state.
gribstream_list_datasets accepts 4 parameters: tag, code, family, is_ensemble. The full parameter table on this page comes from the server's own tool schema.
Register the GribStream MCP server in PolicyLayer and add a rule for gribstream_list_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 GribStream MCP. Nothing to install.
gribstream_list_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 gribstream_list_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 gribstream_list_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.
gribstream_list_datasets is provided by the GribStream MCP server (https://gribstream.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GribStream, and thousands of servers like it.
This server
Across the catalogue