依人氣區間過濾景點（min_pop/max_pop），回傳符合的列表。
AI agents call spots_by_popularity_range 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 database to retrieve attractions matching specified popularity criteria. It performs a read-only retrieval operation with no side effects, no data modification, no execution of arbitrary code, and no destructive or financial implications. The popularity range parameters constrain the query scope, making misuse low-risk.
From the tool's definition Tool name 'spots_by_popularity_range' and description indicating it filters/retrieves spots within a popularity range (min_pop/max_pop) and returns matching list. The action is querying/retrieving data with no modification capability.
Attacks that exploit this kind of access
依人氣區間過濾景點（min_pop/max_pop），回傳符合的列表。. 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_by_popularity_range: 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_by_popularity_range 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_by_popularity_range 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_by_popularity_range. 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_by_popularity_range 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 →