Generate GeoJSON from a SQL query result that includes lat/lng columns. Returns a FeatureCollection for use in maps.
AI agents invoke crow_gis_create_geojson to trigger actions in Crow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool executes a SQL query against a database to retrieve geospatial data and transform it into GeoJSON. The execution of arbitrary SQL queries poses significant risk — depending on the underlying database permissions, a malicious or erroneous query could access sensitive data, perform expensive operations, or (if write permissions exist) modify data.
From the tool's definition Generate GeoJSON from a SQL query result
Documented attack patterns abuse exactly the kind of access crow_gis_create_geojson 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_create_geojson:
{
"version": "1",
"default": "deny",
"tools": {
"crow_gis_create_geojson": {
"limits": [
{
"counter": "crow_gis_create_geojson_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} crow_gis_create_geojson stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate GeoJSON from a SQL query result that includes lat/lng columns. Returns a FeatureCollection for use in maps. It is categorised as a Execute tool in the Crow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Crow MCP server in PolicyLayer and add a rule for crow_gis_create_geojson: 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_create_geojson is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the crow_gis_create_geojson 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_create_geojson. 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_create_geojson 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.