DaedalMap Administrative Boundaries (loc_id to polygon)
com.daedalmap/boundaries
A loc_id to its bounding box, centroid, and polygon, with its name and admin level.
Install surfaces
How DaedalMap Administrative Boundaries (loc_id to polygon) runs, per the official MCP registry entry.
- streamable-http
https://app.daedalmap.com/mcp/boundaries
Governed execution
How KLA gates calls to DaedalMap Administrative Boundaries (loc_id to polygon) once it is connected.
A published policy defines which DaedalMap Administrative Boundaries (loc_id to polygon) actions an agent may take and under what conditions. Each call passes through a policy gate at the tool-call boundary. Permitted actions execute, with the policy basis recorded. Flagged actions execute and are sampled for scheduled human review. High-stakes actions pause and route to a named reviewer on the Decision Desk. The call, the policy decision, and any approval are sealed as an evidence record.
KLA also governs the agent frameworks and model providers you already run. See integrations.