Get full technical details of a specific Swiss dam by name. Returns all available fields: dam type, height, crest length, crest level, reservoir name, impoundment volume, storage level, purpose, operation dates, federal supervision start, and canton. Data source: Swiss Federal Office of Energy (S...
AI agents call get_dam_details 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 queries and retrieves technical metadata about Swiss dams from a public data source (SFOE via swisstopo BGDI). It performs a simple data lookup with no side effects, no state changes, and no capability to modify or delete information. The blast radius of misuse is negligible—an AI agent could only retrieve publicly available technical specifications. This clearly fits the Read category with low severity.
From the tool's definition Tool description states it 'Get[s] full technical details of a specific Swiss dam' and 'Returns all available fields' such as dam type, height, crest length, etc. The verbs are retrieval-only (get, returns).
Attacks that exploit this kind of access
Get full technical details of a specific Swiss dam by name. Returns all available fields: dam type, height, crest length, crest level, reservoir name, impoundment volume, storage level, purpose, operation dates, federal supervision start, and canton. Data source: Swiss Federal Office of Energy (SFOE) via swisstopo BGDI. 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_dam_details: 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_dam_details 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_dam_details 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_dam_details. 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_dam_details 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 →