Load a QGIS project from the specified path.
AI agents call load_project to retrieve information from QGISMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Loading a project is a read-only retrieval operation that queries or fetches data from storage without creating, modifying, or deleting anything. It has minimal side effects—the application state changes to reflect the loaded project, but this is reversible and non-destructive.
From the tool's definition Tool loads/retrieves an existing QGIS project from a file path via 'Load a QGIS project from the specified path.' No modification, deletion, or execution occurs.
Documented attack patterns abuse exactly the kind of access load_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QGISMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for load_project:
{
"version": "1",
"default": "deny",
"tools": {
"load_project": {}
}
}load_project 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.
Load a QGIS project from the specified path. It is categorised as a Read tool in the QGISMCP MCP Server, which means it retrieves data without modifying state.
Register the QGIS 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 QGISMCP. Nothing to install.
load_project 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 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.
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.
load_project is provided by the QGIS MCP server (kicker315/deepseek_qgis_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from QGISMCP, 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.
17 QGISMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.