AI agents call get_project_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 and returns project information without creating, modifying, deleting, executing code, or moving resources. It is a straightforward data retrieval operation with no side effects, fitting the Read category. Severity is low because exposure of project metadata poses minimal security risk—an AI agent cannot cause harm by reading project filenames, coordinate systems, or layer counts.
From the tool's definition Tool retrieves project metadata (filename, title, CRS, layer count, layer summary) with no modification capability. The verb 'Get' and the purely informational nature of the outputs (metadata, counts, summaries) indicate read-only access.
Attacks that exploit this kind of access
Get current project metadata: filename, title, CRS, layer count, and summary of layers. 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_project_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_project_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_project_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_project_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_project_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 →