AI agents call weather_forecast to retrieve information from Maple without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries weather forecast data with no capability to modify, delete, or execute external operations. It is a straightforward data retrieval operation. The low severity reflects that misuse would only result in retrieving irrelevant weather information, posing minimal risk to the system or user data.
From the tool's definition Tool description states 'Get a short multi-day weather forecast for a location' - a retrieval operation with no side effects. Uses Open-Meteo API to query and return weather data.
Attacks that exploit this kind of access
Get a short multi-day weather forecast for a location using Open-Meteo. It is categorised as a Read tool in the Maple MCP Server, which means it retrieves data without modifying state.
Register the Maple MCP server in PolicyLayer and add a rule for weather_forecast: 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 Maple. Nothing to install.
weather_forecast 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 weather_forecast 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 weather_forecast. 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.
weather_forecast is provided by the Maple MCP server (omar2001ramadan/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 →