Disable rate limiting for a specific client, removing any bandwidth restrictions.
AI agents use disableClientRateLimit 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.
This tool modifies network policy/QoS settings by disabling rate limits, which changes configuration state reversibly (the setting can be re-enabled). While it impacts network behavior and could be abused to allow excessive bandwidth consumption by a compromised client, it does not delete data, execute arbitrary code, or move money.
From the tool's definition The tool description states it will 'Disable rate limiting for a specific client, removing any bandwidth restrictions' - this modifies network configuration settings for a client.
Documented attack patterns abuse exactly the kind of access disableClientRateLimit 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 disableClientRateLimit:
{
"version": "1",
"default": "deny",
"tools": {
"disableClientRateLimit": {
"limits": [
{
"counter": "disableclientratelimit_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}disableClientRateLimit 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.
Disable rate limiting for a specific client, removing any bandwidth restrictions. 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 disableClientRateLimit: 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.
disableClientRateLimit 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 disableClientRateLimit 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 disableClientRateLimit. 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.
disableClientRateLimit 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.