AI agents call diagnose 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.
The tool runs diagnostic checks and reports system information (QGIS version, stack status). This is a read-only operation that retrieves and reports information without modifying any data or triggering external operations.
From the tool's definition 'Run diagnostic checks on the QGIS MCP stack. Reports QGIS version'
Attacks that exploit this kind of access
Run diagnostic checks on the QGIS MCP stack. Reports QGIS version,. 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 diagnose: 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.
diagnose 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 diagnose 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 diagnose. 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.
diagnose 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 →