List all layer groups in a workspace. Args: workspace (str): Workspace. Returns: list: Layer group names or info dicts.
AI agents call get_layergroups to retrieve information from GeoServer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing layer group metadata from GeoServer without creating, modifying, deleting, or executing any operations. It is a simple read operation with minimal blast radius—the only risk would be information disclosure if sensitive geospatial layer configurations are exposed, but this is inherent to querying an existing workspace and not a consequence of the tool's design.
From the tool's definition Tool name 'get_layergroups' and description 'List all layer groups in a workspace' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_layergroups 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 get_layergroups:
{
"version": "1",
"default": "deny",
"tools": {
"get_layergroups": {}
}
} get_layergroups 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.
List all layer groups in a workspace. Args: workspace (str): Workspace. Returns: list: Layer group names or info dicts. It is categorised as a Read tool in the GeoServer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GeoServer MCP Server MCP server in PolicyLayer and add a rule for get_layergroups: 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.
get_layergroups 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 get_layergroups 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 get_layergroups. 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.
get_layergroups 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.