AI agents call get_wind_estimate to retrieve information from Windai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries wind resource data for a specified location. The verb 'Get' and the context of fetching estimates (not creating, modifying, or deleting resources) clearly indicates a read-only operation with no side effects. The severity is low because misuse would only return data without causing harm—an agent cannot damage systems or data through this tool.
From the tool's definition Tool name 'get_wind_estimate' and description 'Get an approximate wind resource estimate for any location on Earth' indicate a retrieval operation that queries wind data without modifying or executing anything.
Attacks that exploit this kind of access
Get an approximate wind resource estimate for any location on Earth. It is categorised as a Read tool in the Windai MCP Server, which means it retrieves data without modifying state.
Register the Windai MCP server in PolicyLayer and add a rule for get_wind_estimate: 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 Windai. Nothing to install.
get_wind_estimate 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_estimate 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_estimate. 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_estimate is provided by the Windai MCP server (umedpaliwal/windai-mcp). 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 →