AI agents use scale_geometry 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.
Scaling a geometry transforms/modifies it, which is a Write operation. It creates a new scaled version of the geometry. No irreversible deletion, code execution, or financial implications. Confidence is moderate because the description is minimal and doesn't clarify whether it mutates in place or returns a new object, but in GIS contexts scaling typically produces a modified geometry.
From the tool's definition 'Scale a geometry' — modifies an existing geometry object by scaling it
Documented attack patterns abuse exactly the kind of access scale_geometry 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 scale_geometry:
{
"version": "1",
"default": "deny",
"tools": {
"scale_geometry": {
"limits": [
{
"counter": "scale_geometry_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}scale_geometry 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.
Scale 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 scale_geometry: 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.
scale_geometry 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 scale_geometry 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 scale_geometry. 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.
scale_geometry 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.