// SCAN REPORT

Gogo Backend

10 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 30 Jun 2026

0 can modify or destroy data

10 read-only

10 tools total

Community server · catalogue entry verified 30/06/2026

How to control Gogo Backend ↓

TOOL MAP

What Gogo Backend exposes to your agents

Read (10) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Gogo Backend

PolicyLayer is an MCP gateway — it sits between your AI agents and Gogo Backend, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "get_spots_by_trip_style": {
    "limits": [
      {
        "counter": "get_spots_by_trip_style_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Gogo Backend — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GOGO BACKEND →

Instant setup, no code required.

FULL CATALOGUE

All 10 Gogo Backend tools

READ 10 tools

Read get_spots_by_trip_style 依啟發式標籤過濾；資料來自 get_spots_filtered（先依城市在 DB 篩選，再依人氣排序）。 Read major_views 拿取主要景點，人氣數大於 3000 數，旅遊景點最多可接受 3 個主要景點，最低 1 個。 Read mix_main_and_sub 混合主要/次要景點：main_n=1..3；sub_n=0..2。 Read ping 健康檢查；可選傳入 text 會在回傳 JSON 的 echo 欄位原樣帶回。 Read recommend_itinerary_candidates 先以 get_spots_filtered 在 DB 依城市與人氣取樣；排除 avoid_styles 命中者； Read search_spots 用關鍵字搜尋景點（比對 name/title/description 等常見欄位），回傳前 limit 筆。 Read spots_by_popularity_range 依人氣區間過濾景點（min_pop/max_pop），回傳符合的列表。 Read spots_summary 回傳景點資料摘要（count、min/max/avg 人氣），用於快速檢視資料分佈。 Read sub_views 拿取次要景點，人氣數小於 3000 數。每個主要景點間最少 0 個次要景點，最多 2 個次要景點。 Read top_10_spots 拿取前十個主要景點。

FAQ

Questions about Gogo Backend

Is the Gogo Backend MCP server safe to use without restrictions? +

The Gogo Backend server is primarily read-only with 10 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Gogo Backend MCP server expose? +

10 tools across 1 categories: Read. 10 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Gogo Backend? +

Register the Gogo Backend MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Gogo Backend tool call.

Deterministic rules across all 10 Gogo Backend tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GOGO BACKEND →

Instant setup, no code required.

10 Gogo Backend tools catalogued and risk-classified — across an index of 43,000+ MCP servers.