# get_surf_forecast_by_spot

7 day surf forecast for a named surf spot. Tries saved Global Surfari locations first, then geocodes the name. Example: "Bondi Beach", "Mavericks", "Bells Beach".

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

## Facts

- Tool: `get_surf_forecast_by_spot`
- 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: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | yes | Surf spot or beach name |

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_by_spot",
    "arguments": {
      "name": "<name>"
    }
  }
}
```

## Why get_surf_forecast_by_spot is rated Low

This tool retrieves forecast data (wave, wind, period information) based on a location name. It has no side effects, does not modify data, execute commands, delete anything, or involve financial transactions. It is a straightforward read/query operation that returns informational content to the user.

From the tool's own definition: "Tool provides '7 day surf forecast' data retrieval for a named surf spot with no modification or deletion capabilities. The description explicitly states it 'Tries saved Global Surfari locations first, then geocodes the name' — a pure lookup/query operation."

## Use case

AI agents call get_surf_forecast_by_spot 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_by_spot": {}
  }
}
```

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

- `get_surf_forecast` — Read — https://policylayer.com/tools/com-globalsurfari-globalsurfari/get-surf-forecast.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