AI agents invoke convert_to_geojson to trigger actions in OSM-GeoJSON-MCP-Server. 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.
This tool runs a conversion process on existing files (OSM to GeoJSON), which constitutes executing a transformation operation rather than simply reading data. It processes/transforms file data, which is an Execute-category action. Severity is medium because the blast radius is limited to local file transformation, but misconfiguration could overwrite output files.
From the tool's definition "ダウンロード済みのOSMファイルをGeoJSONに変換" (Convert downloaded OSM files to GeoJSON)
Documented attack patterns abuse exactly the kind of access convert_to_geojson gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OSM-GeoJSON-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for convert_to_geojson:
{
"version": "1",
"default": "deny",
"tools": {
"convert_to_geojson": {
"limits": [
{
"counter": "convert_to_geojson_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}convert_to_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.
ダウンロード済みのOSMファイルをGeoJSONに変換. It is categorised as a Execute tool in the OSM-GeoJSON-MCP-Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OSM-GeoJSON-MCP-Server MCP server in PolicyLayer and add a rule for convert_to_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 OSM-GeoJSON-MCP-Server. Nothing to install.
convert_to_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 convert_to_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 convert_to_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.
convert_to_geojson is provided by the OSM-GeoJSON-MCP-Server MCP server (shimizu/osm-geojson-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OSM-GeoJSON-MCP-Server, 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.
11 OSM-GeoJSON-MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.