Render the current map view to an image file with the specified dimensions.
AI agents use render_map 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 writes an image file to disk based on the current map view. It creates a new file (the rendered image), which is a Write operation. While it reads map data to produce the image, the primary side effect is file creation. It is not Destructive (no data is deleted), not Execute (no code/commands are run), and not Financial.
From the tool's definition Render the current map view to an image file with the specified dimensions
Documented attack patterns abuse exactly the kind of access render_map 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 render_map:
{
"version": "1",
"default": "deny",
"tools": {
"render_map": {
"limits": [
{
"counter": "render_map_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}render_map 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.
Render the current map view to an image file with the specified dimensions. 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 render_map: 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.
render_map 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 render_map 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 render_map. 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.
render_map 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.