指定した都市の風速情報を取得します
AI agents call get_wind_speed 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 information (wind speed) from the Japan Meteorological Agency API for a specified city. It is purely informational with no side effects—it does not create, modify, delete, or execute any external operations. This is a straightforward data retrieval operation, classified as Read with low severity.
From the tool's definition Tool name 'get_wind_speed' and description '指定した都市の風速情報を取得します' (retrieve wind speed information for a specified city) indicate a retrieval operation with no modification or side effects.
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_wind_speed: 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_wind_speed 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_wind_speed 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_wind_speed. 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_wind_speed 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 →