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

gribstream_validate_request

NO AUTH / PUBLIC / READ-ONLY. Validates the basic shape, exact selector tuples, and expression syntax of a proposed GribStream /timeseries or /runs request without sending it. This tool does not execute the request, query weather values, or return forecast data. Use this before returning any hand...

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

This record as markdown: /tools/com-gribstream-mcp/gribstream-validate-request.md

What gribstream_validate_request does on GribStream MCP

AI agents call gribstream_validate_request 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
dataset string Yes Dataset code, for example gfs, ifsoper, nbm, hrrr, or urma.
request object Yes Request body to validate. Omit asOf unless the user explicitly asks for backtesting, time travel, what was known then, or a historical model-run cutoff for /tim
endpoint string Yes Endpoint to validate.

Parameters from the server's own tool schema.

Why gribstream_validate_request is rated Low

Even though gribstream_validate_request only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts freeform code/query input (request.expressions[].expression) · Accepts URL/endpoint input (endpoint) · High parameter count (37 properties)

Questions about gribstream_validate_request

What does the gribstream_validate_request tool do? +

NO AUTH / PUBLIC / READ-ONLY. Validates the basic shape, exact selector tuples, and expression syntax of a proposed GribStream /timeseries or /runs request without sending it. This tool does not execute the request, query weather values, or return forecast data. Use this before returning any hand-edited curl or when changing a request from one dataset to another. 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_validate_request accept? +

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

How do I enforce a policy on gribstream_validate_request? +

Register the GribStream MCP server in PolicyLayer and add a rule for gribstream_validate_request: 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_validate_request? +

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

Can I rate-limit gribstream_validate_request? +

Yes. Add a rate_limit block to the gribstream_validate_request 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_validate_request completely? +

Set action: deny in the PolicyLayer policy for gribstream_validate_request. 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_validate_request? +

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

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