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.
This record as markdown: /tools/com-globalsurfari-globalsurfari/get-surf-forecast.md
What get_surf_forecast does on Global Surfari Surf Forecasts
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.
| 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.
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 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.
Attacks that exploit this kind of access
The rule that runs get_surf_forecast safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Global Surfari Surf Forecasts, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_surf_forecast, this is the rule to start with:
get_surf_forecast 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 Global Surfari Surf Forecasts, apply this rule, and every get_surf_forecast call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Global Surfari Surf Forecasts MCP Server, which means it retrieves data without modifying state.
get_surf_forecast accepts 2 parameters: latitude, longitude. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the Global Surfari Surf Forecasts MCP server in PolicyLayer and add a rule for get_surf_forecast: 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 Global Surfari Surf Forecasts. Nothing to install.
get_surf_forecast 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_surf_forecast 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_surf_forecast. 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_surf_forecast is provided by the Global Surfari Surf Forecasts MCP server (https://globalsurfari.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Global Surfari Surf Forecasts, and thousands of servers like it.
This server
Across the catalogue