getClientHistoryDataEnable

THE RISK

Low Risk

Why getClientHistoryDataEnable needs a policy

This tool retrieves the current state of a history data collection setting on the controller. It performs a read-only query with no side effects, no code execution, and no data modification. The information returned (an enable/disable flag) is non-sensitive operational configuration.

From the tool's definition Tool name 'getClientHistoryDataEnable' and description 'Get the client history data collection enable/disable setting' indicate a retrieval operation that queries a boolean configuration setting without modifying or executing anything.

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

POLICY

How to control getClientHistoryDataEnable

PolicyLayer is an MCP gateway — it sits between your AI agents and Tplink Omada, and nothing reaches the server without passing your rules. This is the rule we recommend for getClientHistoryDataEnable:

policy.json

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

getClientHistoryDataEnable 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 Tplink Omada — 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 Tplink Omada tools

Write disableClientRateLimit Disable rate limiting for a specific client, removing any bandwidth restrictions. Write setClientRateLimit Set custom rate limit (bandwidth control) for a specific client. Specify download and uplo Write setClientRateLimitProfile Apply a predefined rate limit profile to a specific client. Use getRateLimitProfiles to ge Read getAccessControl Get controller access control configuration. Shows which IP ranges are permitted to access Read getAclConfigTypeSetting Get the ACL configuration type setting for the site gateway (L2 or L3 mode). Determines ho Read getAdvancedVpnSetting Get advanced VPN configuration settings for a site, including general VPN parameters and d Read getAlg Get ALG (Application Layer Gateway) configuration for the site gateway. ALG enables inspec Read getAllCloudUsers Get all cloud users configured on the controller, excluding the root account.

All 327 Tplink Omada 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 getClientHistoryDataEnable

What does the getClientHistoryDataEnable tool do? +

Get the client history data collection enable/disable setting for the controller. 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 getClientHistoryDataEnable? +

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

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

Can I rate-limit getClientHistoryDataEnable? +

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

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

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

Enforce policy on every Tplink Omada tool call.

Start from Tplink Omada, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →