Get LLDP (Link Layer Discovery Protocol) global setting for the site. Shows whether LLDP is enabled and which TLVs are advertised.
AI agents call getLldpSetting to retrieve information from Tplink Omada without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves LLDP protocol settings and configuration status. It performs a read-only query of network protocol settings with no side effects, data modification, or destructive capability. The blast radius of misuse is minimal—an attacker would gain visibility into LLDP advertisement configuration but cannot alter network settings or trigger actions.
From the tool's definition Tool name 'getLldpSetting' and description 'Get LLDP...global setting' indicate a retrieval operation that queries configuration state without modifying data.
Documented attack patterns abuse exactly the kind of access getLldpSetting gives an agent:
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 getLldpSetting:
{
"version": "1",
"default": "deny",
"tools": {
"getLldpSetting": {}
}
} getLldpSetting is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get LLDP (Link Layer Discovery Protocol) global setting for the site. Shows whether LLDP is enabled and which TLVs are advertised. 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 getLldpSetting: 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.
getLldpSetting 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 getLldpSetting 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 getLldpSetting. 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.
getLldpSetting 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.
Start from Tplink Omada, 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.
327 Tplink Omada tools catalogued and risk-classified — across an index of 43,000+ MCP servers.