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".
This record as markdown: /tools/com-globalsurfari-globalsurfari/get-surf-forecast-by-spot.md
What get_surf_forecast_by_spot does on Global Surfari Surf Forecasts
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Surf spot or beach name |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs get_surf_forecast_by_spot 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_by_spot, this is the rule to start with:
get_surf_forecast_by_spot 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_by_spot call is checked against it from then on.
Questions about 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". 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_by_spot accepts 1 parameter: name. Required: name. 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_by_spot: 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_by_spot 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_by_spot 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_by_spot. 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_by_spot 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