Get time range (schedule) profiles for a site, listing named time windows that can be applied to firewall rules and access control policies.
AI agents call getScheduleProfile 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 schedule profile information from the TP-Link Omada controller. It has no side effects, does not modify any data, and does not execute commands or policies. The blast radius of misuse is minimal—an attacker could learn about network scheduling policies but cannot change them with this tool alone. Standard Read classification applies.
From the tool's definition "Get time range (schedule) profiles for a site, listing named time windows" - the verb "get" and "listing" indicate data retrieval with no modification. The tool returns configuration data about existing schedule profiles.
Documented attack patterns abuse exactly the kind of access getScheduleProfile 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 getScheduleProfile:
{
"version": "1",
"default": "deny",
"tools": {
"getScheduleProfile": {}
}
}getScheduleProfile 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 time range (schedule) profiles for a site, listing named time windows that can be applied to firewall rules and access control policies. 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 getScheduleProfile: 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.
getScheduleProfile 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 getScheduleProfile 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 getScheduleProfile. 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.
getScheduleProfile 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.