Add a raster layer to the project.
AI agents use add_raster_layer 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.
This tool creates or modifies a QGIS project by adding a raster layer. While reversible (layers can be removed), it constitutes a Write operation as it persistently modifies the project structure. The severity is medium because misuse could clutter or corrupt a project workflow, but the action is non-destructive and doesn't execute arbitrary code or access sensitive external systems directly.
From the tool's definition Tool name 'add_raster_layer' and description 'Add a raster layer to the project' indicate creation/modification of project state by adding a new layer resource.
Documented attack patterns abuse exactly the kind of access add_raster_layer 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 add_raster_layer:
{
"version": "1",
"default": "deny",
"tools": {
"add_raster_layer": {
"limits": [
{
"counter": "add_raster_layer_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_raster_layer 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.
Add a raster layer to the project. 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 add_raster_layer: 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.
add_raster_layer 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 add_raster_layer 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 add_raster_layer. 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.
add_raster_layer 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.