Low Risk

raster_query

raster_query

How to control raster_query ↓

AI agents call raster_query to retrieve information from Gdal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Based on naming convention and context of sibling tools, 'raster_query' most likely retrieves or inspects raster data without modifying it, fitting the Read category. The empty description prevents higher confidence, but the pattern of similar tools (raster_info, raster_stats, vector_query) all being read-only queries supports this classification.

From the tool's definition Tool name is 'raster_query' and sibling tools include 'raster_info', 'raster_stats', 'vector_query', and 'vector_info' which are clearly Read operations. The naming pattern suggests querying/inspection rather than modification.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "raster_query": {}
  }
}

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

  1. Create a free account and register Gdal — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the raster_query tool do? +

raster_query. It is categorised as a Read tool in the Gdal MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on raster_query? +

Register the Gdal MCP server in PolicyLayer and add a rule for raster_query: 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 Gdal. Nothing to install.

What risk level is raster_query? +

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

Can I rate-limit raster_query? +

Yes. Add a rate_limit block to the raster_query 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 raster_query completely? +

Set action: deny in the PolicyLayer policy for raster_query. 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 raster_query? +

raster_query is provided by the Gdal MCP server (jordangunn/gdal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gdal tool call.

Deterministic rules across all 13 Gdal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

13 Gdal tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.