// MCP TOOL REFERENCE

Medium Risk

publish_time_dimension_to_coveragestore

ServerGeoServer MCP Server
CategoryWrite

How to control publish_time_dimension_to_coveragestore ↓

WHAT IT DOES

What publish_time_dimension_to_coveragestore does on GeoServer MCP Server

AI agents use publish_time_dimension_to_coveragestore 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 RISK

Medium Risk

Why publish_time_dimension_to_coveragestore needs a policy

This tool modifies the configuration of a coverage store by adding or updating a time dimension property. While it does not delete data or execute arbitrary code, it creates or updates geospatial metadata that affects how time series data is served. The changes are reversible (can be updated or removed), placing it in the Write category.

From the tool's definition The tool 'publish_time_dimension_to_coveragestore' explicitly performs 'Add or update a time dimension' on a coverage store, which are reversible modification operations that create or alter metadata configurations in GeoServer.

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

POLICY

How to control publish_time_dimension_to_coveragestore

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

policy.json

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

publish_time_dimension_to_coveragestore 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 publish_time_dimension_to_coveragestore

What does the publish_time_dimension_to_coveragestore tool do? +

Add or update a time dimension for a coverage store (for time series). Args: store_name (str, optional): Target coverage store. workspace (str, optional): Workspace. presentation (str, optional): Presentation style. units (str, optional): Time units. default_value (str, optional): Default value for the time dimension. content_type (str, optional): Payload content type. Returns: dict: Response from GeoServer. 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 publish_time_dimension_to_coveragestore? +

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

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

Can I rate-limit publish_time_dimension_to_coveragestore? +

Yes. Add a rate_limit block to the publish_time_dimension_to_coveragestore 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 publish_time_dimension_to_coveragestore completely? +

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

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