Get the convex hull of a geometry.
AI agents call convex_hull 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 convex_hull tool computes and returns a geometric property (the smallest convex polygon containing a set of points) from a provided geometry. This is a pure read operation—it retrieves/calculates derived data with no side effects, no data modification, no code execution, and no destructive actions. Consistent with sibling tools like 'distance', 'centroid', and 'area' which are also geometric calculations/queries.
From the tool's definition Tool name 'convex_hull' and description 'Get the convex hull of a geometry' indicate a computational query operation that derives geometric properties from input data without modifying, deleting, or executing external commands.
Attacks that exploit this kind of access
Get the convex hull 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 convex_hull: 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.
convex_hull 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 convex_hull 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 convex_hull. 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.
convex_hull 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 →