gribstream_list_shared_parameters
NO AUTH / PUBLIC / READ-ONLY. Lists normalized shared parameter presets that can map one logical signal across datasets. This tool does not query weather values and cannot return forecast data.
This record as markdown: /tools/com-gribstream-mcp/gribstream-list-shared-parameters.md
What gribstream_list_shared_parameters does on GribStream MCP
AI agents call gribstream_list_shared_parameters 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 |
|---|---|---|---|
dataset | object | — | Optional dataset code or list of dataset codes to filter supported shared parameters. |
dataset_mode | string | — | Whether every listed dataset must support the preset or any one may support it. |
Parameters from the server's own tool schema.
Why gribstream_list_shared_parameters is rated Low
This tool retrieves and lists parameter presets without querying actual data, modifying state, executing code, or producing destructive/financial effects. It is a straightforward data retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description explicitly states 'NO AUTH / PUBLIC / READ-ONLY' and 'Lists normalized shared parameter presets'. It 'does not query weather values and cannot return forecast data', confirming read-only retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs gribstream_list_shared_parameters 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_shared_parameters, this is the rule to start with:
gribstream_list_shared_parameters 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_shared_parameters call is checked against it from then on.
Questions about gribstream_list_shared_parameters
NO AUTH / PUBLIC / READ-ONLY. Lists normalized shared parameter presets that can map one logical signal across datasets. This tool does not query weather values and cannot return forecast data. It is categorised as a Read tool in the GribStream MCP MCP Server, which means it retrieves data without modifying state.
gribstream_list_shared_parameters accepts 2 parameters: dataset, dataset_mode. 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_shared_parameters: 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_shared_parameters 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_shared_parameters 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_shared_parameters. 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_shared_parameters 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