get_datastore

THE RISK

Low Risk

Why get_datastore needs a policy

The tool queries and retrieves information about a datastore configuration without modifying, deleting, or executing any operations. It takes workspace and datastore name as parameters and returns descriptive data. This is a straightforward read operation typical of API query endpoints.

From the tool's definition Tool name is 'get_datastore' and description states it 'Get a specific datastore by name' and 'Returns: dict: Datastore description.' This is a retrieval operation with no side effects.

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

POLICY

How to control get_datastore

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_datastore": {}
  }
}

get_datastore is read-only, so it stays allowed — but 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.

CAP 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 →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_datastore

What does the get_datastore tool do? +

Get a specific datastore by name. Args: workspace (str): Workspace name. name (str): Datastore name. Returns: dict: Datastore description. It is categorised as a Read tool in the GeoServer MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_datastore? +

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

get_datastore is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_datastore? +

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

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

get_datastore 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 →