AI agents call find_facilities 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.
The tool is part of a server providing 'direct access to historical air quality, ERA5 meteorology, water risk, geocoding, and industrial facility data.' The name 'find_facilities' most naturally maps to a Read operation—retrieving or querying facility location/information data. No description is available to indicate destructive, write, execute, or financial operations.
From the tool's definition Tool named 'find_facilities' with no description provided. Based on naming convention and context within a data access API (alongside geocoding, climate queries, and water risk tools), this appears to be a facility lookup/search operation.
Attacks that exploit this kind of access
find_facilities. 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 find_facilities: 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.
find_facilities 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 find_facilities 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 find_facilities. 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.
find_facilities 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 →