travel__check_destination_crowd
［2027 連假與訂票］查某個目的地在一段日期的人潮等級：是否撞到當地國定假日或旺季。country 國碼：JP,KR,HK,CN,VN,TH,SG,PH,ID,US,GB,FR,AU
This record as markdown: /tools/com-penguindriver-hub/travel--check-destination-crowd.md
What travel__check_destination_crowd does on AI 代理人任務中樞
AI agents call travel__check_destination_crowd to retrieve information from AI 代理人任務中樞 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | string | Yes | YYYY-MM-DD |
start | string | Yes | YYYY-MM-DD |
country | string | Yes |
Parameters from the server's own tool schema.
Why travel__check_destination_crowd is rated Low
Even though travel__check_destination_crowd only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs travel__check_destination_crowd safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AI 代理人任務中樞, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For travel__check_destination_crowd, this is the rule to start with:
travel__check_destination_crowd is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AI 代理人任務中樞, apply this rule, and every travel__check_destination_crowd call is checked against it from then on.
Questions about travel__check_destination_crowd
［2027 連假與訂票］查某個目的地在一段日期的人潮等級：是否撞到當地國定假日或旺季。country 國碼：JP,KR,HK,CN,VN,TH,SG,PH,ID,US,GB,FR,AU. It is categorised as a Read tool in the AI 代理人任務中樞 MCP Server, which means it retrieves data without modifying state.
travel__check_destination_crowd accepts 3 parameters: end, start, country. Required: end, start, country. The full parameter table on this page comes from the server's own tool schema.
Register the AI 代理人任務中樞 MCP server in PolicyLayer and add a rule for travel__check_destination_crowd: 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 AI 代理人任務中樞. Nothing to install.
travel__check_destination_crowd 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 travel__check_destination_crowd 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 travel__check_destination_crowd. 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.
travel__check_destination_crowd is provided by the AI 代理人任務中樞 MCP server (https://hub.penguindriver.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AI 代理人任務中樞, and thousands of servers like it.
This server
Across the catalogue