DaedalMap Geocoding and Reverse Geocoding (loc_id)
com.daedalmap/geocoding
Reverse geocode latitude/longitude to loc_id; resolve loc_ids to boundaries, centroids, hierarchy.
Install surfaces
How DaedalMap Geocoding and Reverse Geocoding (loc_id) runs, per the official MCP registry entry.
- streamable-http
https://app.daedalmap.com/mcp/geography
Governed execution
How KLA gates calls to DaedalMap Geocoding and Reverse Geocoding (loc_id) once it is connected.
A published policy defines which DaedalMap Geocoding and Reverse Geocoding (loc_id) 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.