spatial_join
AI agents call spatial_join to retrieve information from LocuSync Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Spatial join operations in GIS typically combine attributes from two datasets based on spatial relationships (e.g., point-in-polygon), returning correlated results without altering underlying data. The presence of similar analytical tools (centroid, distance, area) and absence of destructive or write-enabled siblings support Read classification.
From the tool's definition Tool name 'spatial_join' combined with context of sibling tools (area, centroid, distance, elevation) and server description emphasizing 'spatial analysis' and 'coordinate transformations' suggests a geospatial query operation that retrieves or correlates…
Attacks that exploit this kind of access
spatial_join. It is categorised as a Read tool in the LocuSync Server MCP Server, which means it retrieves data without modifying state.
Register the LocuSync Server MCP server in PolicyLayer and add a rule for spatial_join: 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 LocuSync Server. Nothing to install.
spatial_join 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_join 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_join. 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_join is provided by the LocuSync Server MCP server (matbel91765/gis-mcp-server). 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 →