AI agents use set_layer_visibility to create or update resources in QGIS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QGIS MCP environment.
This tool modifies layer visibility state but does not delete data or execute arbitrary code. The change is reversible (visibility can be toggled back), making it a Write operation rather than Destructive. Severity is medium because toggling layer visibility in a collaborative GIS environment could obscure important information or cause confusion, but the impact is limited to display state and easily correctable.
From the tool's definition Tool name is 'set_layer_visibility' with description 'Set a layer'. The verb 'set' combined with 'visibility' indicates modification of layer properties (show/hide), which alters the state of a GIS project reversibly.
Attacks that exploit this kind of access
Set a layer. It is categorised as a Write tool in the QGIS MCP 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 set_layer_visibility: 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. Nothing to install.
set_layer_visibility 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 set_layer_visibility 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 set_layer_visibility. 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.
set_layer_visibility is provided by the QGIS MCP server (nkarasiak/qgis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →