Get the centroid (center point) of a geometry.
AI agents call centroid 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.
The centroid tool performs a pure calculation on geometric input data to derive a center point coordinate. This is a read-only operation with no side effects, no data modification, no code execution, and no irreversible actions. The blast radius if misused is minimal—an agent could only extract geometric information. This aligns clearly with the 'Read' category for retrieval and query operations.
From the tool's definition The tool description states 'Get the centroid (center point) of a geometry.' This is a retrieval operation that computes and returns a derived spatial property from input geometry without modifying any data or triggering external operations.
Attacks that exploit this kind of access
Get the centroid (center point) of a geometry. 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 centroid: 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.
centroid 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 centroid 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 centroid. 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.
centroid 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 →