依啟發式標籤過濾；資料來自 get_spots_filtered（先依城市在 DB 篩選，再依人氣排序）。
AI agents call get_spots_by_trip_style 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 tool queries a PostgreSQL database to return curated travel destination data based on user-specified trip style preferences. It performs read-only operations (filtering and sorting) without creating, modifying, deleting, or executing external code. The severity is low because the worst outcome of misuse is returning irrelevant travel recommendations, with minimal blast radius.
From the tool's definition The tool filters and retrieves travel spot data by trip style using heuristic tags, with results sourced from database queries (filtering by city, then sorting by popularity).
Attacks that exploit this kind of access
依啟發式標籤過濾；資料來自 get_spots_filtered（先依城市在 DB 篩選，再依人氣排序）。. 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 get_spots_by_trip_style: 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.
get_spots_by_trip_style 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 get_spots_by_trip_style 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 get_spots_by_trip_style. 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.
get_spots_by_trip_style 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 →