AI agents call get_raster_info 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 queries metadata and properties of raster data (dimensions, CRS, statistics, nodata values) with no side effects. It performs information retrieval only, fitting the 'Read' category. The low severity reflects that retrieving GIS layer metadata poses minimal risk - it cannot modify, delete, execute code, or cause financial impact even if misused by an AI agent.
From the tool's definition Tool retrieves information about raster layers without modifying or deleting data. The description explicitly states it gets 'band count, dimensions, CRS, extent, per-band statistics, nodata values' - all read-only query operations.
Attacks that exploit this kind of access
Get raster layer info: band count, dimensions, CRS, extent, per-band statistics, nodata values. 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_raster_info: 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_raster_info 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_raster_info 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_raster_info. 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_raster_info 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 →