AI agents call water_risk to retrieve information from Jiskta without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to query or retrieve water risk data from the Jiskta API based on context clues. No language suggests data creation, modification, deletion, code execution, or financial operations.
From the tool's definition Tool name 'water_risk' combined with server description indicating it 'provides AI assistants with direct access to...water risk...data via the Jiskta API'.
Attacks that exploit this kind of access
water_risk. It is categorised as a Read tool in the Jiskta MCP Server, which means it retrieves data without modifying state.
Register the Jiskta MCP server in PolicyLayer and add a rule for water_risk: 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 Jiskta. Nothing to install.
water_risk 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 water_risk 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 water_risk. 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.
water_risk is provided by the Jiskta MCP server (jiskta/jiskta-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 →