AI agents call get_layer_features to retrieve information from QGIS MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries feature data from a vector layer without side effects. It performs no creation, modification, deletion, or code execution. The operation is a pure read that returns spatial feature attributes. No data is altered, no external operations are triggered, and the action is fully idempotent, making it a straightforward Read category tool with low severity.
From the tool's definition Tool name 'get_layer_features' and description 'Get features from a vector layer' indicate data retrieval only. The phrase 'Flat dicts: _fid + attributes at top level' describes the output format, not any modification or execution.
Attacks that exploit this kind of access
Get features from a vector layer. Flat dicts: _fid + attributes at top level. It is categorised as a Read tool in the QGIS MCP MCP Server, which means it retrieves data without modifying state.
Register the QGIS MCP server in PolicyLayer and add a rule for get_layer_features: 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.
get_layer_features 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 get_layer_features 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 get_layer_features. 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.
get_layer_features 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 →