Low Risk

get_all_users

List all users in the GeoServer instance. Returns: list: Usernames or user info dicts.

How to control get_all_users ↓

What get_all_users does on GeoServer MCP Server

AI agents call get_all_users 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.

Low Risk

Why get_all_users needs a policy

This tool retrieves user information from the GeoServer instance without creating, modifying, or deleting any data. It is purely a query/read operation. However, the exposure of user lists can enable enumeration attacks or help identify targets for privilege escalation, warranting medium severity in the context of AI agent misuse.

From the tool's definition Tool name 'get_all_users' and description 'List all users in the GeoServer instance' indicate a data retrieval operation with no modification side effects.

Risk signalsBulk/mass operation — affects multiple targets

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

How to control get_all_users

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_all_users": {}
  }
}

get_all_users is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_all_users

What does the get_all_users tool do? +

List all users in the GeoServer instance. Returns: list: Usernames or user info dicts. 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_all_users? +

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

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

Can I rate-limit get_all_users? +

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

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

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

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.