hurricane_tracker
Currently-active hurricanes and tropical systems from NOAA NHC, with category, wind/pressure, current position, movement, and forecast cone link.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/hurricane-tracker.md
What hurricane_tracker does on Livedatalink
AI agents call hurricane_tracker to retrieve information from Livedatalink 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 |
|---|---|---|---|
basin | string | — | Optional basin filter: 'AL' (Atlantic), 'EP' (Eastern Pacific), 'CP' (Central Pacific). |
Parameters from the server's own tool schema.
Why hurricane_tracker is rated Low
This tool queries and returns real-time meteorological data with no side effects. It performs a read-only lookup of public weather information, presenting no risk of data modification, code execution, or resource damage if misused by an AI agent.
From the tool's definition Tool retrieves currently-active hurricanes and tropical systems data from NOAA NHC with category, wind/pressure, position, movement, and forecast information. No modification, execution, deletion, or financial transaction capability described.
Attacks that exploit this kind of access
The rule that runs hurricane_tracker safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hurricane_tracker, this is the rule to start with:
hurricane_tracker is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every hurricane_tracker call is checked against it from then on.
Questions about hurricane_tracker
Currently-active hurricanes and tropical systems from NOAA NHC, with category, wind/pressure, current position, movement, and forecast cone link. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
hurricane_tracker accepts 1 parameter: basin. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for hurricane_tracker: 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 Livedatalink. Nothing to install.
hurricane_tracker 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 hurricane_tracker 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 hurricane_tracker. 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.
hurricane_tracker is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue