Set custom rate limit (bandwidth control) for a specific client. Specify download and upload limits in Kbps. This configures custom limits directly without using a predefined profile.
AI agents use setClientRateLimit to create or update resources in Tplink Omada — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tplink Omada environment.
The tool creates or modifies bandwidth control settings for network clients, which is reversible and does not delete data or execute arbitrary code. It falls under Write category (modifies network configuration). Severity is medium because misuse could degrade network service for targeted clients, but effects are reversible and limited in blast radius compared to destructive or financial operations.
From the tool's definition Tool description states 'Set custom rate limit (bandwidth control) for a specific client' and 'configures custom limits directly' — this is a modification action that changes client network configuration settings.
Documented attack patterns abuse exactly the kind of access setClientRateLimit 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 setClientRateLimit:
{
"version": "1",
"default": "deny",
"tools": {
"setClientRateLimit": {
"limits": [
{
"counter": "setclientratelimit_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}setClientRateLimit stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set custom rate limit (bandwidth control) for a specific client. Specify download and upload limits in Kbps. This configures custom limits directly without using a predefined profile. It is categorised as a Write tool in the Tplink Omada MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tplink Omada MCP server in PolicyLayer and add a rule for setClientRateLimit: 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.
setClientRateLimit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setClientRateLimit 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 setClientRateLimit. 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.
setClientRateLimit 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.