Create a new project a save it
AI agents use create_new_project to create or update resources in QGISMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QGISMCP environment.
Creating and saving a new project is a reversible data creation operation. While it modifies the filesystem and initiates a new GIS project, the action is not destructive (can be undone by deleting the project file) and does not execute arbitrary code or trigger external operations. It falls clearly into the Write category.
From the tool's definition Tool description states 'Create a new project a save it' — indicates creation and persistence of a new file/project resource with no deletion or irreversibility involved.
Documented attack patterns abuse exactly the kind of access create_new_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 create_new_project:
{
"version": "1",
"default": "deny",
"tools": {
"create_new_project": {
"limits": [
{
"counter": "create_new_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_new_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.
Free to start. No card required.
Create a new project a save it. It is categorised as a Write tool in the QGISMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the QGIS MCP server in PolicyLayer and add a rule for create_new_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.
create_new_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_new_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 create_new_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.
create_new_project is provided by the QGIS MCP server (syauqi-uqi/qgis_mcp_modify1). 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.
15 QGISMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.