geo_polygon
Analyse GeoJSON polygons (Polygon, MultiPolygon, Feature or FeatureCollection): geodesic area (m², km², ha, acres; same spherical formula as Turf.js), perimeter, area-weighted centroid, bounding box, validity report (unclosed or short rings, self-intersections, RFC 7946 winding order), point-in-p...
This record as markdown: /tools/com-it-scorptech-x402/geo-polygon.md
What geo_polygon does on ScorpTech x402 API
AI agents call geo_polygon to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
hull | boolean | — | Return the convex hull (of the geometry, or of points when no geometry is given) |
points | array | — | Points to test, each [lon, lat] |
geometry | object | — | GeoJSON Polygon / MultiPolygon / Feature / FeatureCollection ([lon, lat] order) |
simplify | number | — | Douglas-Peucker tolerance in metres (returns simplified geometry) |
Parameters from the server's own tool schema.
Why geo_polygon is rated Low
Even though geo_polygon only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs geo_polygon safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For geo_polygon, this is the rule to start with:
geo_polygon is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every geo_polygon call is checked against it from then on.
Questions about geo_polygon
Analyse GeoJSON polygons (Polygon, MultiPolygon, Feature or FeatureCollection): geodesic area (m², km², ha, acres; same spherical formula as Turf.js), perimeter, area-weighted centroid, bounding box, validity report (unclosed or short rings, self-intersections, RFC 7946 winding order), point-in-polygon tests for up to 1,000 points honouring holes and edges, convex hull and optional Douglas-Peucker simplification to a tolerance in metres. Offline. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/geo-polygon. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
geo_polygon accepts 4 parameters: hull, points, geometry, simplify. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for geo_polygon: 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 ScorpTech x402 API. Nothing to install.
geo_polygon 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 geo_polygon 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 geo_polygon. 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.
geo_polygon is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue