Split a raster into square tiles of a given size and save them individually. Parameters: - source: input raster path. - tile_size: size of each tile (e.g., 256 or 512). - destination_dir: directory to store the tiles.
AI agents use tile_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.
This tool performs a geospatial data transformation that writes output files to disk. While it modifies the file system by creating new tiles, the operation is reversible and non-destructive—the original raster remains unchanged and the output tiles can be deleted. There is no deletion, overwrite of existing critical data, code execution, or financial impact.
From the tool's definition Tool 'tile_raster' creates and saves new raster tile files to a destination directory. The description explicitly states 'save them individually' to 'destination_dir'. This is a file creation operation with reversible effects (created tiles can be deleted).
Documented attack patterns abuse exactly the kind of access tile_raster 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 tile_raster:
{
"version": "1",
"default": "deny",
"tools": {
"tile_raster": {
"limits": [
{
"counter": "tile_raster_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}tile_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.
Free to start. No card required.
Split a raster into square tiles of a given size and save them individually. Parameters: - source: input raster path. - tile_size: size of each tile (e.g., 256 or 512). - destination_dir: directory to store the tiles. 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 tile_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.
tile_raster 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 tile_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.
Set action: deny in the PolicyLayer policy for tile_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.
tile_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.
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.