This record as markdown: /tools/creativelead-unclick/willyweather-surf.md
What willyweather_surf does on UnClick
AI agents call willyweather_surf to retrieve information from UnClick 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 |
|---|---|---|---|
days | number | — | |
api_key | string | — | |
location_id | number | — |
Parameters from the server's own tool schema.
Why willyweather_surf is rated Low
This tool retrieves surf condition data from WillyWeather without creating, modifying, deleting, or executing operations. It is a straightforward read/query operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'willyweather_surf' and description 'Get surf report from WillyWeather' indicate data retrieval only. The verb 'Get' and context of fetching a weather/surf report confirm no side effects or modifications.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs willyweather_surf safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For willyweather_surf, this is the rule to start with:
willyweather_surf 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 UnClick, apply this rule, and every willyweather_surf call is checked against it from then on.
Questions about willyweather_surf
Get surf report from WillyWeather. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
willyweather_surf accepts 3 parameters: days, api_key, location_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for willyweather_surf: 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 UnClick. Nothing to install.
willyweather_surf 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 willyweather_surf 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 willyweather_surf. 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.
willyweather_surf is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue