Clip a raster dataset using polygons from a shapefile and write the result. Converts the shapefile's CRS to match the raster's CRS if they are different. Parameters: - raster_path_or_url: local path or HTTPS URL of the source raster. - shapefile_path: local filesystem path to a .shp file containi...
AI agents use clip_raster_with_shapefile 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.
The tool creates a new raster file at a specified destination path by clipping an input raster with polygon boundaries. This is a reversible write operation—the output can be deleted or overwritten. While it modifies the filesystem, it does not delete existing data irreversibly (Destructive), execute arbitrary code (Execute), or involve financial transactions.
From the tool's definition Tool description states it will 'write the result' and 'destination: local path where the masked raster will be written.' This is a data creation/modification operation that produces a new file artifact.
Documented attack patterns abuse exactly the kind of access clip_raster_with_shapefile gives an agent:
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 clip_raster_with_shapefile:
{
"version": "1",
"default": "deny",
"tools": {
"clip_raster_with_shapefile": {
"limits": [
{
"counter": "clip_raster_with_shapefile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}clip_raster_with_shapefile 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.
Free to start. No card required.
Clip a raster dataset using polygons from a shapefile and write the result. Converts the shapefile's CRS to match the raster's CRS if they are different. Parameters: - raster_path_or_url: local path or HTTPS URL of the source raster. - shapefile_path: local filesystem path to a .shp file containing polygons. - destination: local path where the masked raster will be written. 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.
Register the GIS MCP Server MCP server in PolicyLayer and add a rule for clip_raster_with_shapefile: 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.
clip_raster_with_shapefile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the clip_raster_with_shapefile 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 clip_raster_with_shapefile. 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.
clip_raster_with_shapefile 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.
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.