天气信息查询 - 根据经纬度查询天气信息，使用Open-Meteo API。如果不提供日期，默认查询今天和明天的天气数据
AI agents call getWeatherByLocation to retrieve information from Flight Ticket MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves weather information by querying an external API (Open-Meteo) based on latitude/longitude coordinates. It performs a read-only operation that returns data without creating, modifying, deleting, or executing any operations. The default behavior of querying today's and tomorrow's weather data confirms it is a simple data retrieval function with no adverse effects if misused by an AI agent.
From the tool's definition Tool description indicates it is a weather information query ('天气信息查询 - 根据经纬度查询天气信息') that retrieves data based on coordinates using Open-Meteo API. The tool only queries and returns weather data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access getWeatherByLocation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Flight Ticket MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getWeatherByLocation:
{
"version": "1",
"default": "deny",
"tools": {
"getWeatherByLocation": {}
}
}getWeatherByLocation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
天气信息查询 - 根据经纬度查询天气信息，使用Open-Meteo API。如果不提供日期，默认查询今天和明天的天气数据. It is categorised as a Read tool in the Flight Ticket MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Flight Ticket MCP Server MCP server in PolicyLayer and add a rule for getWeatherByLocation: 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 Flight Ticket MCP Server. Nothing to install.
getWeatherByLocation 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 getWeatherByLocation 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 getWeatherByLocation. 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.
getWeatherByLocation is provided by the Flight Ticket MCP Server MCP server (xiaonieli7/flightticketmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Flight Ticket MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 Flight Ticket MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.