Reverse geocode: convert latitude/longitude to an address. Zoom level controls detail (3=country, 10=city, 14=suburb, 18=building).
AI agents call crow_gis_reverse to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries a geocoding service to look up address information based on coordinates. It has no side effects, does not modify data, does not execute arbitrary code, and does not involve financial transactions. The zoom level parameter only controls the granularity of the returned address data, not any destructive or executable behavior. This is a standard Read operation.
From the tool's definition Tool performs reverse geocoding which 'convert[s] latitude/longitude to an address' with zoom level controls for detail. This is a read-only query operation that retrieves geographical data without modifying, deleting, or executing external commands.
Documented attack patterns abuse exactly the kind of access crow_gis_reverse gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_gis_reverse:
{
"version": "1",
"default": "deny",
"tools": {
"crow_gis_reverse": {}
}
}crow_gis_reverse is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Reverse geocode: convert latitude/longitude to an address. Zoom level controls detail (3=country, 10=city, 14=suburb, 18=building). It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_gis_reverse: 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 Crow. Nothing to install.
crow_gis_reverse 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 crow_gis_reverse 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 crow_gis_reverse. 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.
crow_gis_reverse is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.