New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

gribstream_resolve_shared_parameter

NO AUTH / PUBLIC / READ-ONLY. Resolves one shared parameter preset for a dataset, returning native variables and expressions to use in /timeseries or /runs request bodies. This tool does not execute the request, query weather values, or return forecast data.

SERVERGribStream MCP SOURCEhttps://gribstream.com/mcp
Low RISK CLASS
Category Read
Parameters 31 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-gribstream-mcp/gribstream-resolve-shared-parameter.md

What gribstream_resolve_shared_parameter does on GribStream MCP

AI agents call gribstream_resolve_shared_parameter 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.

ParameterTypeRequiredDescription
alias string Optional output alias for the resolved request.
dataset string Optional dataset code to resolve the shared parameter against.
parameter string Yes Shared parameter code, for example temperature_2m, wind_speed_10m, mean_sea_level_pressure, or wind_speed_500hpa.

Parameters from the server's own tool schema.

Why gribstream_resolve_shared_parameter is rated Low

The tool purely resolves and returns metadata about a shared parameter preset (variables and expressions). It performs no writes, executions, or data retrieval of actual weather values. Explicitly described as read-only with no side effects.

From the tool's definition NO AUTH / PUBLIC / READ-ONLY. Resolves one shared parameter preset for a dataset, returning native variables and expressions... This tool does not execute the request, query weather values, or return forecast data.

Questions about gribstream_resolve_shared_parameter

What does the gribstream_resolve_shared_parameter tool do? +

NO AUTH / PUBLIC / READ-ONLY. Resolves one shared parameter preset for a dataset, returning native variables and expressions to use in /timeseries or /runs request bodies. This tool does not execute the request, query weather values, or return forecast data. It is categorised as a Read tool in the GribStream MCP MCP Server, which means it retrieves data without modifying state.

What parameters does gribstream_resolve_shared_parameter accept? +

gribstream_resolve_shared_parameter accepts 3 parameters: alias, dataset, parameter. Required: parameter. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gribstream_resolve_shared_parameter? +

Register the GribStream MCP server in PolicyLayer and add a rule for gribstream_resolve_shared_parameter: 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.

What risk level is gribstream_resolve_shared_parameter? +

gribstream_resolve_shared_parameter is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gribstream_resolve_shared_parameter? +

Yes. Add a rate_limit block to the gribstream_resolve_shared_parameter 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.

How do I block gribstream_resolve_shared_parameter completely? +

Set action: deny in the PolicyLayer policy for gribstream_resolve_shared_parameter. 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.

What MCP server provides gribstream_resolve_shared_parameter? +

gribstream_resolve_shared_parameter 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GribStream's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.