getAllLocalUsers

Get all local users configured on the controller, excluding the root account.

SERVERTplink Omada SOURCEmigueltvms/tplink-omada-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/migueltvms-tplink-omada-mcp/getalllocalusers.md

WHAT IT DOES

What getAllLocalUsers does on Tplink Omada

AI agents call getAllLocalUsers to retrieve information from Tplink Omada without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why getAllLocalUsers is rated Low

This tool queries and returns a list of local users from the TP-Link Omada controller. It performs a read-only operation that retrieves existing data without creating, modifying, deleting, or executing any actions. While user account information could be considered sensitive, the tool itself poses minimal risk as it only exposes already-configured data.

From the tool's definition Tool name 'getAllLocalUsers' and description 'Get all local users configured on the controller' indicate a retrieval operation with no modification or side effects.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getAllLocalUsers safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tplink Omada, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getAllLocalUsers, this is the rule to start with:

getAllLocalUsers Allowed

getAllLocalUsers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tplink Omada, apply this rule, and every getAllLocalUsers call is checked against it from then on.

FAQ

Questions about getAllLocalUsers

What does the getAllLocalUsers tool do? +

Get all local users configured on the controller, excluding the root account. It is categorised as a Read tool in the Tplink Omada MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getAllLocalUsers? +

Register the Tplink Omada MCP server in PolicyLayer and add a rule for getAllLocalUsers: 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 Tplink Omada. Nothing to install.

What risk level is getAllLocalUsers? +

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

Can I rate-limit getAllLocalUsers? +

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

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

getAllLocalUsers is provided by the Tplink Omada MCP server (migueltvms/tplink-omada-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tplink Omada, and thousands of servers like it.

This server

All 327 Tplink Omada tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →