AI agents call query_climate_point 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.
Despite the empty description, the naming pattern and server context strongly indicate this tool retrieves climate/meteorology data (likely ERA5 historical data by point location). No side effects, modifications, deletions, financial transactions, or code execution are implied. This is a data retrieval operation.
From the tool's definition Tool name 'query_climate' with '_point' suffix suggests querying meteorological data. Server description states it provides access to 'historical air quality, ERA5 meteorology' data.
Attacks that exploit this kind of access
query_climate_point. 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 query_climate_point: 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.
query_climate_point 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 query_climate_point 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 query_climate_point. 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.
query_climate_point 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 →