create_workspace

THE RISK

Medium Risk

Why create_workspace needs a policy

This tool creates new configuration objects (workspaces) in GeoServer, which is a write operation that modifies system state. The action is reversible (workspaces can be deleted), so it does not qualify as Destructive. The operation does not execute arbitrary code, delete data irreversibly, or involve financial transactions.

From the tool's definition Tool name is 'create_workspace' and description states 'Create a new workspace in GeoServer', which is a reversible creation operation that modifies the GeoServer configuration.

Documented attack patterns abuse exactly the kind of access create_workspace gives an agent:

POLICY

How to control create_workspace

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_workspace:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_workspace": {
      "limits": [
        {
          "counter": "create_workspace_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_workspace 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.

Create a free account and register GeoServer MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GeoServer MCP Server tools

Destructive delete_coveragestore Delete a coveragestore from a workspace. Args: workspace (str): Workspace Destructive delete_layergroup Delete a layer group from a workspace. Args: workspace (str): Workspace. Destructive delete_resource Delete a resource from GeoServer. Args: resource_type: Type of resource t Destructive delete_user Delete a user by name. Args: username (str): User to remove. Returns: Destructive delete_usergroup Delete a user group. Args: name (str): Name of group to remove. Retur Destructive remove_layer_from_layergroup Remove a layer from a group. Args: layer_name (str): Layer. layer Destructive reset_geoserver Reset all GeoServer caches/connections. Returns: str: Result message from Execute reload_geoserver Reload catalog and config from disk. Returns: str: Result message from re

All 56 GeoServer MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_workspace

What does the create_workspace tool do? +

Create a new workspace in GeoServer. Args: workspace: Name of the workspace to create Returns: Dict with status and result information. 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.

How do I enforce a policy on create_workspace? +

Register the GeoServer MCP Server MCP server in PolicyLayer and add a rule for create_workspace: 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.

What risk level is create_workspace? +

create_workspace is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_workspace? +

Yes. Add a rate_limit block to the create_workspace 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.

How do I block create_workspace completely? +

Set action: deny in the PolicyLayer policy for create_workspace. 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.

What MCP server provides create_workspace? +

create_workspace 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.

Enforce policy on every GeoServer MCP Server tool call.

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.

CHECK YOUR STACK →