AI agents call get_weather_history to retrieve information from Mcp Swiss without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical weather information from Swiss stations. It is a simple query/fetch operation that reads existing data without creating, modifying, deleting, or executing any operations. No financial impact or destructive capability is present. The low severity reflects minimal risk even if misused by an AI agent, as the worst case would be excessive querying of public historical weather data.
From the tool's definition Tool name 'get_weather_history' and description 'Get historical weather data for a Swiss station' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get historical weather data for a Swiss station. It is categorised as a Read tool in the Mcp Swiss MCP Server, which means it retrieves data without modifying state.
Register the Mcp Swiss MCP server in PolicyLayer and add a rule for get_weather_history: 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 Swiss. Nothing to install.
get_weather_history 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_history 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_history. 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_history is provided by the Mcp Swiss MCP server (mcp-swiss). 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 →