回傳景點資料摘要（count、min/max/avg 人氣），用於快速檢視資料分佈。
AI agents call spots_summary 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.
The `spots_summary` tool performs read-only operations: it aggregates statistics (count, min/max/avg popularity metrics) from the travel spot database. This is a classic Read operation—querying data with no side effects, no modification, and no execution of arbitrary code. The low severity reflects minimal risk even if misused by an agent, as it only exposes aggregate statistics about attractions.
From the tool's definition Tool description indicates it returns spot data summary (count, min/max/avg popularity) for quick data overview. The function is purely retrieving and aggregating existing data without modification or deletion.
Attacks that exploit this kind of access
回傳景點資料摘要（count、min/max/avg 人氣），用於快速檢視資料分佈。. 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 spots_summary: 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.
spots_summary 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 spots_summary 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 spots_summary. 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.
spots_summary 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 →