AI agents call get_water_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 hydrological data (water levels) from Swiss stations. It is a read-only operation that queries existing public data without creating, modifying, deleting, or executing any operations. The action verb 'Get' and the nature of historical data access confirm this is a simple read operation with minimal risk.
From the tool's definition Tool name 'get_water_history' and description 'Get historical river/lake water level data' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get historical river/lake water level data for a Swiss hydrological 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_water_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_water_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_water_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_water_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_water_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 →