Compute histogram of pixel values for each band. Parameters: - source: path to input raster. - bins: number of histogram bins.
AI agents call raster_histogram to retrieve information from GIS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
raster_histogram performs a geospatial analysis query on existing raster data without side effects. It retrieves statistical information (pixel value distribution) from a file specified by the user. The tool has minimal blast radius if misused by an agent—it cannot corrupt data, execute code, or affect systems beyond reading a file and computing statistics.
From the tool's definition Tool computes and returns histogram statistics of pixel values from a raster file. No parameters allow modification of the source data, file deletion, or external system commands.
Documented attack patterns abuse exactly the kind of access raster_histogram 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 raster_histogram:
{
"version": "1",
"default": "deny",
"tools": {
"raster_histogram": {}
}
} raster_histogram is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Compute histogram of pixel values for each band. Parameters: - source: path to input raster. - bins: number of histogram bins. It is categorised as a Read tool in the GIS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GIS MCP Server MCP server in PolicyLayer and add a rule for raster_histogram: 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.
raster_histogram is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the raster_histogram 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 raster_histogram. 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.
raster_histogram 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.