load_geodata · Ontario Data MCP: Risk & Policy

WHAT IT DOES

What load_geodata does on Ontario Data

AI agents use load_geodata to create or update resources in Ontario Data — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ontario Data environment.

WHY IT NEEDS A POLICY

Why load_geodata needs a policy

The tool downloads a geospatial resource and writes it into a local DuckDB cache. This is a Write operation (creates/modifies local data by caching) rather than pure Read (it has side effects on the local database). It is not Destructive since it is a cache write that can be reversed, and not Execute since it does not run arbitrary code or commands.

From the tool's definition 'Download and cache a geospatial resource... into DuckDB with spatial support' — it fetches external data and writes/caches it into a local DuckDB database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

load_geodata Rate-limited

load_geodata stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "load_geodata": {
      "limits": [
        {
          "counter": "load_geodata_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ontario Data, so you can run agents against it safely.

FAQ

Questions about load_geodata

What does the load_geodata tool do? +

Download and cache a geospatial resource (SHP, KML, GeoJSON) into DuckDB with spatial support. It is categorised as a Write tool in the Ontario Data MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on load_geodata? +

Register the Ontario Data MCP server in PolicyLayer and add a rule for load_geodata: 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 Ontario Data. Nothing to install.

What risk level is load_geodata? +

load_geodata is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit load_geodata? +

Yes. Add a rate_limit block to the load_geodata 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.

How do I block load_geodata completely? +

Set action: deny in the PolicyLayer policy for load_geodata. 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.

What MCP server provides load_geodata? +

load_geodata is provided by the Ontario Data MCP server (sprine/ontario-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.