getServiceProfile

Get service type profiles for a site (paginated), listing protocol/port definitions used in firewall rules.

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

WHAT IT DOES

What getServiceProfile does on Tplink Omada

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

This tool retrieves service profile information (protocol/port definitions) from the Omada controller. The verb 'Get' and the absence of any language indicating modification, deletion, or execution of commands confirm this is a read operation. The information retrieved is configuration metadata, not sensitive data requiring destructive capabilities.

From the tool's definition Tool name 'getServiceProfile' and description 'Get service type profiles for a site (paginated), listing protocol/port definitions used in firewall rules' indicate read-only retrieval of configuration data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

getServiceProfile Allowed

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

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

FAQ

Questions about getServiceProfile

What does the getServiceProfile tool do? +

Get service type profiles for a site (paginated), listing protocol/port definitions used in firewall rules. 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 getServiceProfile? +

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

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

Can I rate-limit getServiceProfile? +

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

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

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