AI agents call search_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.
This tool retrieves or queries surf spot data by name without modifying, deleting, or executing external operations. It is a straightforward read operation that returns matching spot information.
From the tool's definition Tool name 'search_spots' and description 'Search surf spots by name' indicate a query/search operation with no side effects.
Attacks that exploit this kind of access
Search surf spots by name. 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 search_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.
search_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 search_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 search_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.
search_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 →