// SCAN REPORT

GeoServer MCP Server

56 tools. 33 can modify or destroy data without limits.

7 destructive tools with no built-in limits. Policy required.

Last updated:

33 can modify or destroy data
23 read-only
56 tools total

Community server · catalogue entry verified 11/06/2026

How to control GeoServer MCP Server ↓

TOOL MAP

What GeoServer MCP Server exposes to your agents

Read (23) Write / Execute (25) Destructive / Financial (7)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS
Critical Risk

The most dangerous GeoServer MCP Server tools

Destructive · High delete_coveragestore This tool irreversibly deletes geospatial data infrastructure (a coveragestore) and cannot be undone. Destructive · High delete_layergroup This tool permanently removes a layer group from a workspace without the ability to undo the operation. Destructive · Critical delete_resource This tool irreversibly deletes data from GeoServer. Destructive · High delete_user User deletion is an irreversible operation that cannot be undone without manual intervention or backup restoration.

33 of GeoServer MCP Server's 56 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control GeoServer MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and GeoServer MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "delete_coveragestore": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "add_layer_to_layergroup": {
    "limits": [
      {
        "counter": "add_layer_to_layergroup_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get_all_usergroups": {
    "limits": [
      {
        "counter": "get_all_usergroups_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register GeoServer MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON GEOSERVER →

Free to start. No card required.

FULL CATALOGUE

All 56 GeoServer MCP Server tools

DESTRUCTIVE 7 tools
Destructive delete_coveragestore Delete a coveragestore from a workspace. Args: workspace (str): Workspace name. name Destructive delete_layergroup Delete a layer group from a workspace. Args: workspace (str): Workspace. name (str): Destructive delete_resource Delete a resource from GeoServer. Args: resource_type: Type of resource to delete (workspace, Destructive delete_user Delete a user by name. Args: username (str): User to remove. Returns: dict: Delet Destructive delete_usergroup Delete a user group. Args: name (str): Name of group to remove. Returns: dict: Re Destructive remove_layer_from_layergroup Remove a layer from a group. Args: layer_name (str): Layer. layer_workspace (str): La Destructive reset_geoserver Reset all GeoServer caches/connections. Returns: str: Result message from reset operation.
EXECUTE 1 tools
Execute reload_geoserver Reload catalog and config from disk. Returns: str: Result message from reload.
WRITE 24 tools
Write add_layer_to_layergroup Add a specific layer to a layer group. Args: layer_name (str): Layer to add. layer_wo Write create_catagorized_featurestyle Create a categorized style for features (polygon, line, point) using column values. Args: style_n Write create_classified_featurestyle Create a classified style for features using distinct column values/classes. Args: style_name (st Write create_coveragestore Create a new coveragestore in a workspace. Args: workspace (str): Workspace name. nam Write create_coveragestyle Create a raster coverage style (colormap, ...) Args: style_name (str): Name for the style. Write create_datastore Create a new datastore in the given workspace. Args: workspace (str): Name of the workspace t Write create_featurestore Create a new featurestore in the given workspace. Args: workspace (str): Target workspace. Write create_gpkg_datastore Create a GeoPackage (GPKG) datastore. Args: workspace (str): Workspace name. name (st Write create_layer Create a new layer in GeoServer. Args: workspace: The workspace for the new layer lay Write create_layergroup Create a new layer group with specific layers and (optionally) styles. Args: workspace (str): Write create_outline_featurestyle Create a simple outline-only style for features. Args: style_name (str): Style name. outl Write create_shp_datastore Create an ESRI Shapefile datastore. Args: workspace (str): Workspace in GeoServer. na Write create_style Create a new SLD style in GeoServer. Args: name: Name for the style sld: SLD XML cont Write create_user Create a new user for GeoServer security. Args: username (str): New user's name. password Write create_usergroup Create a new user group. Args: name (str): Name for the user group. users (list, opti Write create_workspace Create a new workspace in GeoServer. Args: workspace: Name of the workspace to create Write edit_featuretype Edit the settings of a feature type in a store. Args: workspace (str): Workspace containing s Write modify_user Modify an existing user's properties (password, enabled state, properties, etc). Args: userna Write publish_featurestore Publish an existing featurestore. Args: workspace (str): Target workspace. store_name (st Write publish_featurestore_sqlview Publish a featurestore using a SQL view definition. Args: workspace (str): Workspace context. Write publish_style Assign/publish a style to a layer. Args: layer_name (str): The target layer. style_name ( Write publish_time_dimension_to_coveragestore Add or update a time dimension for a coverage store (for time series). Args: store_name (str, opt Write update_layergroup Update a layer group's details and configuration. Args: layergroup_name (str): The group to u Write update_service Update selected OGC service options. Args: service (str): Service (e.g., 'wfs', 'wms').
READ 23 tools
Read get_all_usergroups Return all user groups. Returns: list: Names or info dicts for all groups. Read get_all_users List all users in the GeoServer instance. Returns: list: Usernames or user info dicts. Read get_coveragestore Get details about a single coveragestore. Args: workspace (str): Workspace. name (str Read get_coveragestores Get all coveragestores in a workspace. Args: workspace (str): Name of the workspace. Retu Read get_datastore Get a specific datastore by name. Args: workspace (str): Workspace name. name (str): Read get_datastores List all datastores in the given workspace. Args: workspace (str): Workspace. Returns: Read get_feature_attribute Get feature attribute schema/details. Args: workspace (str): Workspace. store_name (s Read get_featuretypes List all feature types in a given store. Args: workspace (str): Workspace. store_name Read get_layer_info Get detailed information about a layer. Args: workspace: The workspace containing the layer Read get_layergroup Get a layer group from a workspace. Args: workspace (str): Workspace to search. name Read get_layergroups List all layer groups in a workspace. Args: workspace (str): Workspace. Returns: Read get_manifest Get GeoServer manifest metadata/details. Returns: dict: Manifest metadata from GeoServer. Read get_status Obtain general server status. Returns: dict: Status/health report. Read get_system_status Get system status overview/info from GeoServer. Returns: dict: System info (CPU, memory, etc) Read get_version Fetch GeoServer version string. Returns: str: GeoServer version. Read list_layers List layers in GeoServer, optionally filtered by workspace. Args: workspace: Optional workspa Read list_workspaces List available workspaces in GeoServer. Read query_features Query features from a vector layer using CQL filter. Args: workspace: The workspace containin Read style_catagorize_xml Generate SLD for categorized vector style (SVG fill/block display). Args: column_name (str): Colum Read style_classified_xml Get SLD XML for classified vector style. Args: style_name (str): Name of style. column_nam Read style_coverage_style_xml Generate XML for raster/coverage SLD. Args: color_ramp: Color ramp (list, dict...) style_n Read generate_map Generate a map image using WMS GetMap. Args: layers: List of layers to include (format: works Read style_outline_only_xml XML for outline-only style for a geometry. Args: color (str): Outline color (hex). width (
OTHER 1 tools
Other style_coverage_style_colormapentry Generate color map entries for raster SLD. Args: color_ramp: List/dict of colors. min_valu
EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Sperax Ecosystem Crypto & DeFI MCP Server 1318 tools
admin
Mcp Afip 1300 tools
admin
Mcp Ap2 1300 tools
admin
BNB Chain MCP 1240 tools
admin
Nodebench 824 tools
admin
Amazon Bedrock Knowledge Base Retrieval MCP Server 805 tools
admin
Amazon Data Processing MCP Server 805 tools
admin
Amazon ECS MCP Server 805 tools
admin
FAQ

Questions about GeoServer MCP Server

Can an AI agent delete data through the GeoServer MCP Server MCP server? +

Yes. The GeoServer MCP Server server exposes 7 destructive tools including delete_coveragestore, delete_layergroup, delete_resource. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through GeoServer MCP Server? +

The GeoServer MCP Server server has 24 write tools including add_layer_to_layergroup, create_catagorized_featurestyle, create_classified_featurestyle. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach GeoServer MCP Server.

How many tools does the GeoServer MCP Server MCP server expose? +

56 tools across 3 categories: Destructive, Read, Write. 23 are read-only. 33 can modify, create, or delete data.

How do I enforce a policy on GeoServer MCP Server? +

Register the GeoServer MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every GeoServer MCP Server tool call.

Deterministic rules across all 56 GeoServer MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GEOSERVER →

Free to start. No card required.

56 GeoServer MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.