Get climate observations from NOAA Climate Data Online. Returns historical weather measurements such as temperature, precipitation, and snowfall. You must provide either a station_id or a FIPS code to identify the location, and a date range. Args: station_id: NOAA station identifier (e.g. 'GHCND:...
Part of the NOAA Climate Data server.
Free to start. No card required.
AI agents call get_climate_data to retrieve information from NOAA Climate Data without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_climate_data only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_climate_data": {}
}
}See the full NOAA Climate Data policy for all 3 tools.
These attack patterns abuse exactly the kind of access get_climate_data gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get climate observations from NOAA Climate Data Online. Returns historical weather measurements such as temperature, precipitation, and snowfall. You must provide either a station_id or a FIPS code to identify the location, and a date range. Args: station_id: NOAA station identifier (e.g. 'GHCND:USW00094728' for Central Park). fips: FIPS code for county or state (e.g. '36' for New York state, '36061' for Manhattan). dataset: Dataset ID. Common values: 'GHCND' (daily summaries), 'GSOM' (monthly), 'GSOY' (annual), 'NORMAL_DLY' (daily normals). Default is 'GHCND'. start_date: Start date in YYYY-MM-DD format. Required for most datasets. end_date: End date in YYYY-MM-DD format. Required for most datasets. data_types: Comma-separated data type IDs to filter. Common types: TMAX (max temp), TMIN (min temp), TAVG (avg temp), PRCP (precipitation), SNOW (snowfall), SNWD (snow depth), AWND (avg wind speed). If omitted, all available types are returned. limit: Maximum number of records to return (default 100, max 1000).. It is categorised as a Read tool in the NOAA Climate Data MCP Server, which means it retrieves data without modifying state.
Register the NOAA Climate Data MCP server in PolicyLayer and add a rule for get_climate_data: 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 NOAA Climate Data. Nothing to install.
get_climate_data 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 get_climate_data 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 get_climate_data. 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.
get_climate_data is provided by the NOAA Climate Data MCP server (https://mcp.olyport.com/noaa-climate/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 NOAA Climate Data tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.