Low Risk

noaa_find_stations

Search for weather observation stations by location, bounding box, dataset, and data type. Returns station IDs, names, coordinates, elevation, and data coverage dates. Filter by locationId (e.g., "FIPS:37" for all NC stations), extent (lat/lon bounding box), datasetId, datatypeId, and date range....

Risk signalsHigh parameter count (11 properties)

Part of the Noaa Cdo Mcp Server server.

noaa_find_stations is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE NOAA CDO MCP SERVER →

Free to start. No card required.

AI agents call noaa_find_stations to retrieve information from Noaa Cdo Mcp Server 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 noaa_find_stations 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "noaa_find_stations": {}
  }
}

See the full Noaa Cdo Mcp Server policy for all 7 tools.

Get this rule live on your own Noaa Cdo Mcp Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NOAA CDO MCP SERVER →

These attack patterns abuse exactly the kind of access noaa_find_stations gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so noaa_find_stations only ever does what you allow.

SECURE NOAA CDO MCP SERVER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the noaa_find_stations tool do? +

Search for weather observation stations by location, bounding box, dataset, and data type. Returns station IDs, names, coordinates, elevation, and data coverage dates. Filter by locationId (e.g., "FIPS:37" for all NC stations), extent (lat/lon bounding box), datasetId, datatypeId, and date range. Station IDs returned here are used as stationId in noaa_fetch_data. A station must have data for the dataset and date range you want — filter by datasetId and startDate/endDate to ensure compatibility. Common station ID formats: GHCND:USC00450974, COOP:010008.. It is categorised as a Read tool in the Noaa Cdo Mcp Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on noaa_find_stations? +

Register the Noaa Cdo Mcp Server MCP server in PolicyLayer and add a rule for noaa_find_stations: 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 Cdo Mcp Server. Nothing to install.

What risk level is noaa_find_stations? +

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

Can I rate-limit noaa_find_stations? +

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

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

noaa_find_stations is provided by the Noaa Cdo Mcp Server MCP server (@cyanheads/noaa-cdo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Noaa Cdo Mcp Server tool call.

Deterministic rules across all 7 Noaa Cdo Mcp Server 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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.