Create a new layer group with specific layers and (optionally) styles. Args: workspace (str): The workspace for the group. name (str): Name of the layer group. layers (list): List of layers to include. styles (list, optional): List of styles for layers. Returns: dict: Creation result.
AI agents use create_layergroup to create or update resources in GeoServer MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GeoServer MCP Server environment.
The tool creates new geospatial layer groups, which is a reversible modification operation. This fits the Write category as it adds new configuration/data to the GeoServer instance without destructive intent. Severity is medium because misconfiguration could impact geospatial service availability or expose unintended data layers, but the operation is reversible (the layer group can be deleted).
From the tool's definition Tool description explicitly states 'Create a new layer group' with arguments for workspace, name, layers, and styles. Returns 'Creation result' indicating data is created and persisted in GeoServer.
Documented attack patterns abuse exactly the kind of access create_layergroup gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GeoServer MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_layergroup:
{
"version": "1",
"default": "deny",
"tools": {
"create_layergroup": {
"limits": [
{
"counter": "create_layergroup_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_layergroup 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 new layer group with specific layers and (optionally) styles. Args: workspace (str): The workspace for the group. name (str): Name of the layer group. layers (list): List of layers to include. styles (list, optional): List of styles for layers. Returns: dict: Creation result. It is categorised as a Write tool in the GeoServer MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GeoServer MCP Server MCP server in PolicyLayer and add a rule for create_layergroup: 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 GeoServer MCP Server. Nothing to install.
create_layergroup 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 create_layergroup 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 create_layergroup. 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.
create_layergroup is provided by the GeoServer MCP Server MCP server (mahdin75/geoserver-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GeoServer 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.
56 GeoServer MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.