AI agents invoke get_wind_farm_assessment to trigger actions in Windai. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool executes an AI deep learning model inference pipeline on WindAI's backend. This is an external computational operation whose results depend on the input arguments (location, parameters). It does not merely read cached data — it actively runs a model. No financial transaction, deletion, or data modification is implied, so Execute is the most appropriate category.
From the tool's definition 'Run a full WindAI AI-powered wind resource assessment using our deep learning model' — 'Run' indicates triggering an external AI/ML computation pipeline
Attacks that exploit this kind of access
Run a full WindAI AI-powered wind resource assessment using our deep learning model. It is categorised as a Execute tool in the Windai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Windai MCP server in PolicyLayer and add a rule for get_wind_farm_assessment: 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_farm_assessment is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the get_wind_farm_assessment 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_farm_assessment. 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_farm_assessment 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 →