AI agents call list_spots to retrieve information from Surf without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name 'list_spots' and the context of sibling tools that are all retrieval-oriented (get_spot_info, get_tides, get_forecast, find_spots), this tool almost certainly retrieves or queries surf spot data without side effects.
From the tool's definition Tool name 'list_spots' and sibling tools including 'list_regions', 'get_spot_info', 'search_spots', and 'get_forecast' all indicate data retrieval operations.
Attacks that exploit this kind of access
list_spots. It is categorised as a Read tool in the Surf MCP Server, which means it retrieves data without modifying state.
Register the Surf MCP server in PolicyLayer and add a rule for list_spots: 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 Surf. Nothing to install.
list_spots 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 list_spots 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 list_spots. 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.
list_spots is provided by the Surf MCP server (steph76k/surf-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →