get_project_info

THE RISK

Low Risk

Why get_project_info needs a policy

This tool retrieves or queries project metadata without causing side effects. It is a read-only operation that returns information about the state of the current project in QGIS, consistent with the Read category definition (retrieves or queries data; no side effects).

From the tool's definition Tool name 'get_project_info' and description 'Get current project information' indicate retrieval of metadata about the current QGIS project. No modification, deletion, or execution of operations is described.

Documented attack patterns abuse exactly the kind of access get_project_info gives an agent:

POLICY

How to control get_project_info

PolicyLayer is an MCP gateway — it sits between your AI agents and QGISMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_project_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_project_info": {}
  }
}

get_project_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register QGISMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More QGISMCP tools

Destructive remove_layer Remove a layer from the project by its ID. Execute execute_code Execute arbitrary PyQGIS code provided as a string. Execute execute_processing Execute a processing algorithm with the given parameters. Execute zoom_to_layer Zoom to the extent of a specified layer. Write add_raster_layer Add a raster layer to the project. Write add_vector_layer Add a vector layer to the project. Write create_new_project Create a new project a save it Write save_project Save the current project to the given path, or to the current project path if not specifie

All 15 QGISMCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_project_info

What does the get_project_info tool do? +

Get current project information. It is categorised as a Read tool in the QGISMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_project_info? +

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 QGISMCP. Nothing to install.

What risk level is get_project_info? +

get_project_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_project_info? +

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.

How do I block get_project_info completely? +

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.

What MCP server provides get_project_info? +

get_project_info is provided by the QGIS MCP server (syauqi-uqi/qgis_mcp_modify1). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every QGISMCP tool call.

Start from QGISMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →