spatial_weights
AI agents call spatial_weights 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 weights calculations are analytical operations that query or derive metrics from geospatial data without creating, modifying, deleting, or executing external operations. The empty description lowers confidence slightly, but the server context and sibling tools suggest this performs statistical analysis. Without evidence of side effects or external execution, this maps to Read category with low severity.
From the tool's definition Tool name 'spatial_weights' is part of a geospatial analysis server alongside other analysis tools like 'area', 'buffer', 'centroid', 'distance'.
Attacks that exploit this kind of access
spatial_weights. 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_weights: 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_weights 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_weights 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_weights. 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_weights 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 →