getClientHistoryDataEnable
Get the client history data collection enable/disable setting for the controller.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getclienthistorydataenable.md
What getClientHistoryDataEnable does on Tplink Omada
AI agents call getClientHistoryDataEnable 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.
Why getClientHistoryDataEnable is rated Low
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.
Attacks that exploit this kind of access
The rule that runs getClientHistoryDataEnable 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 getClientHistoryDataEnable, this is the rule to start with:
getClientHistoryDataEnable is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tplink Omada, apply this rule, and every getClientHistoryDataEnable call is checked against it from then on.
Questions about getClientHistoryDataEnable
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.
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.
getClientHistoryDataEnable is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
More on Tplink Omada, and thousands of servers like it.
This server
Across the catalogue