Medium Risk

resample_raster

resample_raster

How to control resample_raster ↓

What resample_raster does on GIS MCP Server

AI agents use resample_raster to create or update resources in GIS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GIS MCP Server environment.

Medium Risk

Why resample_raster needs a policy

Resampling a raster typically involves reading input raster data and writing a new output raster at a different resolution or alignment. This is a Write operation as it creates/modifies data. However, the empty description significantly lowers confidence. Given the GIS context and sibling tools involving raster operations (clip_raster_with_shapefile), resampling is a standard GIS write operation.

From the tool's definition Tool name 'resample_raster' suggests modifying/transforming raster data by changing its resolution or grid structure; description is empty and uninformative.

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

How to control resample_raster

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "resample_raster": {
      "limits": [
        {
          "counter": "resample_raster_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

resample_raster stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register GIS MCP Server — 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about resample_raster

What does the resample_raster tool do? +

resample_raster. It is categorised as a Write tool in the GIS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on resample_raster? +

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

What risk level is resample_raster? +

resample_raster is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit resample_raster? +

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

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

resample_raster is provided by the GIS MCP Server MCP server (mahdin75/gis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GIS MCP Server tool call.

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

Free to start. No card required.

98 GIS MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.