用關鍵字搜尋景點（比對 name/title/description 等常見欄位），回傳前 limit 筆。
AI agents call search_spots to retrieve information from Gogo Backend without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries a database for travel spot data matching user-provided keywords. It retrieves and returns information with no side effects, reversible changes, code execution, data destruction, or financial implications. The tool is part of a travel data access server designed for read-only retrieval of curated attractions.
From the tool's definition Tool name 'search_spots' and description indicate keyword search functionality that 'retrieves' attractions by matching against name/title/description fields and returning results up to a limit.
Attacks that exploit this kind of access
用關鍵字搜尋景點（比對 name/title/description 等常見欄位），回傳前 limit 筆。. It is categorised as a Read tool in the Gogo Backend MCP Server, which means it retrieves data without modifying state.
Register the Gogo Backend 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 Gogo Backend. 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 Gogo Backend MCP server (jjjtyy666/gogo-backend-mcp6). 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 →