指定した都市の天気概況を取得します
AI agents call get_weather_overview to retrieve information from MCP-Weather without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves weather data from the Japan Meteorological Agency API without creating, modifying, or deleting any data. It is a pure read operation with no adverse effects if misused by an AI agent—returning incorrect or fabricated weather data poses minimal risk compared to other capability categories.
From the tool's definition Tool name 'get_weather_overview' and description indicate retrieval of weather overview data ('天気概況を取得します' = 'retrieve weather overview'). Server description confirms 'retrieval of weather information' with no side effects mentioned.
Attacks that exploit this kind of access
指定した都市の天気概況を取得します. It is categorised as a Read tool in the MCP-Weather MCP Server, which means it retrieves data without modifying state.
Register the MCP-Weather MCP server in PolicyLayer and add a rule for get_weather_overview: 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 MCP-Weather. Nothing to install.
get_weather_overview 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_weather_overview 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_weather_overview. 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_weather_overview is provided by the MCP-Weather MCP server (takatoshi-miura/mcp-weather). 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 →