load_project

THE RISK

Medium Risk

Why load_project needs a policy

Loading a project modifies the current QGIS session state by replacing or opening a project file. This is a Write operation as it changes the application's working state. It is not destructive (the file itself is not deleted), not purely read-only (it changes active session state), and not execute (no code/commands are run).

From the tool's definition Load a QGIS project from the specified path

Documented attack patterns abuse exactly the kind of access load_project gives an agent:

POLICY

How to control load_project

PolicyLayer is an MCP gateway — it sits between your AI agents and QGIS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for load_project:

policy.json

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

load_project 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.

Create a free account and register QGIS MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More QGIS MCP Server tools

Destructive remove_layer Remove a layer from the project by its ID. Execute execute_code Execute arbitrary PyQGIS code provided as a string. Execute execute_processing Execute a processing algorithm with the given parameters. Execute zoom_to_layer Zoom to the extent of a specified layer. Write render_map Render the current map view to an image file with the specified dimensions. Write add_raster_layer Add a raster layer to the project. Write add_vector_layer Add a vector layer to the project. Write create_new_project Create a new project a save it

All 15 QGIS MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about load_project

What does the load_project tool do? +

Load a QGIS project from the specified path. It is categorised as a Write tool in the QGIS MCP Server 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_project? +

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

What risk level is load_project? +

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

Can I rate-limit load_project? +

Yes. Add a rate_limit block to the load_project 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_project completely? +

Set action: deny in the PolicyLayer policy for load_project. 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_project? +

load_project is provided by the QGIS MCP Server MCP server (jjsantos01/qgis_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every QGIS MCP Server tool call.

Start from QGIS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →