getPpskNetworkProfile
List Private PSK (PPSK) network profiles for a site by type. Returns profile names, authentication mode, and associated RADIUS server settings.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getppsknetworkprofile.md
What getPpskNetworkProfile does on Tplink Omada
AI agents call getPpskNetworkProfile 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 getPpskNetworkProfile is rated Low
This tool retrieves and lists configuration information about PPSK network profiles for a site. It has no side effects, does not execute commands, does not modify data, and does not trigger external operations. It is a straightforward read operation similar to other list/get tools on the server (getAllDeviceBySite, getAllRoles, etc.).
From the tool's definition Tool description states 'List Private PSK (PPSK) network profiles' and 'Returns profile names, authentication mode, and associated RADIUS server settings' — purely a retrieval/query operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs getPpskNetworkProfile 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 getPpskNetworkProfile, this is the rule to start with:
getPpskNetworkProfile 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 getPpskNetworkProfile call is checked against it from then on.
Questions about getPpskNetworkProfile
List Private PSK (PPSK) network profiles for a site by type. Returns profile names, authentication mode, and associated RADIUS server settings. 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 getPpskNetworkProfile: 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.
getPpskNetworkProfile 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 getPpskNetworkProfile 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 getPpskNetworkProfile. 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.
getPpskNetworkProfile 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