AI agents use buffer 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 buffer operation produces new geometric objects derived from existing ones. While it creates data, the operation is reversible (buffers can be removed or recalculated) and does not destroy existing data. It is not Read (it produces output beyond simple retrieval), not Execute (no arbitrary code or external operations triggered by variable arguments), not Destructive (no irreversible deletion), and not Financial.
From the tool's definition The tool 'buffer' creates a buffer around a geometry, which generates new geometric data structures. This is a data creation operation that modifies the geospatial dataset by adding computed geometries, fitting the Write category of creating or modifying data…
Documented attack patterns abuse exactly the kind of access buffer 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 buffer:
{
"version": "1",
"default": "deny",
"tools": {
"buffer": {
"limits": [
{
"counter": "buffer_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}buffer 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.
Create a buffer around a geometry. 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 buffer: 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.
buffer 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 buffer 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 buffer. 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.
buffer 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.