Add a specific layer to a layer group. Args: layer_name (str): Layer to add. layer_workspace (str): Workspace for the layer. layergroup_name (str): Target group name. layergroup_workspace (str, optional): Workspace for the group. Returns: dict: Status and any info.
AI agents use add_layer_to_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.
This tool creates or modifies data (the layergroup membership) in a reversible manner—a layer can be removed from a group. It does not execute arbitrary code, delete data irreversibly, or move financial resources. It is a Write operation because it changes the state of geospatial data structures in GeoServer.
From the tool's definition The tool description explicitly states it will "Add a specific layer to a layer group," which is a create/modify operation.
Documented attack patterns abuse exactly the kind of access add_layer_to_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 add_layer_to_layergroup:
{
"version": "1",
"default": "deny",
"tools": {
"add_layer_to_layergroup": {
"limits": [
{
"counter": "add_layer_to_layergroup_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_layer_to_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.
Add a specific layer to a layer group. Args: layer_name (str): Layer to add. layer_workspace (str): Workspace for the layer. layergroup_name (str): Target group name. layergroup_workspace (str, optional): Workspace for the group. Returns: dict: Status and any info. 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 add_layer_to_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.
add_layer_to_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 add_layer_to_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 add_layer_to_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.
add_layer_to_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.