# get_surf_forecast

7 day surf forecast (wave height in feet, wave period in seconds, wind speed in mph, wind direction in degrees) for the nearest coastal forecast point to a latitude/longitude. Data from NOAA wave models.

Agent View of the PolicyLayer registry record for `get_surf_forecast`. HTML page: https://policylayer.com/tools/com-globalsurfari-globalsurfari/get-surf-forecast

## Facts

- Tool: `get_surf_forecast`
- Server: Global Surfari Surf Forecasts (`https://globalsurfari.com/mcp`) — https://policylayer.com/tools/com-globalsurfari-globalsurfari.md
- Homepage: https://github.com/https://globalsurfari.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `latitude` | number | yes | Latitude in decimal degrees (-90 to 90) |
| `longitude` | number | yes | Longitude in decimal degrees (-180 to 180) |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_surf_forecast",
    "arguments": {
      "latitude": 0,
      "longitude": 0
    }
  }
}
```

## Why get_surf_forecast is rated Low

This is a straightforward data retrieval operation. The tool fetches pre-computed meteorological forecast data from NOAA without creating, modifying, or deleting anything. There are no side effects or irreversible actions. The blast radius of misuse is minimal—an agent could only retrieve forecast information for various locations, which poses no security, financial, or operational risk.

From the tool's own definition: "Tool retrieves a '7 day surf forecast' with wave, wind, and period data from NOAA models. The description uses retrieval language ('forecast for') with no modification, creation, or deletion of data. It queries existing forecast data by coordinates."

## Use case

AI agents call get_surf_forecast to retrieve information from Global Surfari Surf Forecasts without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Global Surfari Surf Forecasts:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_surf_forecast": {}
  }
}
```

## Other tools on Global Surfari Surf Forecasts (2)

- `get_surf_forecast_by_spot` — Read — https://policylayer.com/tools/com-globalsurfari-globalsurfari/get-surf-forecast-by-spot.md
- `list_surf_spots` — Read — https://policylayer.com/tools/com-globalsurfari-globalsurfari/list-surf-spots.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-globalsurfari-globalsurfari · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-globalsurfari-globalsurfari