getClient

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/getclient.md

WHAT IT DOES

What getClient does on Tplink Omada

AI agents call getClient 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 getClient is rated Low

This tool retrieves client information from the Omada controller without modifying, deleting, or executing any operations. It performs a simple lookup/filter operation on existing data. There are no side effects, no code execution, and no data modification capabilities. This is a straightforward Read operation with low severity since client information exposure is generally low-risk in a network management context.

From the tool's definition Tool description states 'Fetch details for a specific Omada client' and 'filters the site client list in-process'. The verb 'Fetch' and 'filters' indicate data retrieval with no modifications.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getClient 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 getClient, this is the rule to start with:

getClient Allowed

getClient 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": {
    "getClient": {}
  }
}

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 getClient call is checked against it from then on.

FAQ

Questions about getClient

What does the getClient tool do? +

[DEPRECATED] Use listClients instead. When you have a client MAC, getClientDetail is also available. This tool filters the site client list in-process to emulate a per-client lookup. Fetch details for a specific Omada client. 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 getClient? +

Register the Tplink Omada MCP server in PolicyLayer and add a rule for getClient: 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 getClient? +

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

Can I rate-limit getClient? +

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

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

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