noaa.weather.forecast

Get 7-day weather forecast for a US location by latitude/longitude. Returns day and night periods with temperature (°F), precipitation chance, wind speed/direction, and detailed forecast text. Powered by NOAA National Weather Service (api.weather.gov). US contiguous only.

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/noaa.weather.forecast.md

WHAT IT DOES

What noaa.weather.forecast does on Apibase

AI agents call noaa.weather.forecast 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
`latitude`	number	Yes	Latitude in decimal degrees (US contiguous only: 24–50)
`longitude`	number	Yes	Longitude in decimal degrees (US contiguous only: −125 to −66)

Parameters from the server's own tool schema.

RISK

Why noaa.weather.forecast is rated Low

Retrieves public weather forecast data with no side effects or state modifications.

From the tool's definition Get 7-day weather forecast, Returns day and night periods with temperature

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs noaa.weather.forecast 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 noaa.weather.forecast, this is the rule to start with:

noaa.weather.forecast Allowed

noaa.weather.forecast is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "noaa.weather.forecast": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every noaa.weather.forecast call is checked against it from then on.

FAQ

Questions about noaa.weather.forecast

What does the noaa.weather.forecast tool do? +

What parameters does noaa.weather.forecast accept? +

noaa.weather.forecast accepts 2 parameters: latitude, longitude. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on noaa.weather.forecast? +

Register the Apibase MCP server in PolicyLayer and add a rule for noaa.weather.forecast: 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.

What risk level is noaa.weather.forecast? +

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

Can I rate-limit noaa.weather.forecast? +

Yes. Add a rate_limit block to the noaa.weather.forecast 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 noaa.weather.forecast completely? +

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

noaa.weather.forecast 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →