AI agents call spatial_link 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.
Based on the server's purpose (providing data access) and the pattern of sibling tools being predominantly Read operations (geocoding, querying climate data, finding facilities), spatial_link most likely performs a spatial data linking or lookup function. The name 'spatial_link' suggests associating or linking spatial data rather than modifying it.
From the tool's definition Tool name 'spatial_link' and server context (Jiskta API providing access to historical air quality, meteorology, water risk, geocoding, and industrial facility data) suggest a data linking or querying operation.
Attacks that exploit this kind of access
spatial_link. 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 spatial_link: 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.
spatial_link 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 spatial_link 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 spatial_link. 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.
spatial_link 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 →