Apply a predefined rate limit profile to a specific client. Use getRateLimitProfiles to get available profile IDs.
AI agents use setClientRateLimitProfile 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 client rate limiting configuration, which is a state change that affects network behavior for a target client. However, it is reversible and does not delete data or execute arbitrary code. It falls under Write category rather than Execute because it applies a predefined configuration rather than executing arbitrary commands.
From the tool's definition Tool name 'setClientRateLimitProfile' and description 'Apply a predefined rate limit profile to a specific client' indicate modification of client network settings. The action is reversible (a different profile can be applied or the setting changed back).
Documented attack patterns abuse exactly the kind of access setClientRateLimitProfile 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 setClientRateLimitProfile:
{
"version": "1",
"default": "deny",
"tools": {
"setClientRateLimitProfile": {
"limits": [
{
"counter": "setclientratelimitprofile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}setClientRateLimitProfile 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.
Apply a predefined rate limit profile to a specific client. Use getRateLimitProfiles to get available profile IDs. 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 setClientRateLimitProfile: 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.
setClientRateLimitProfile 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 setClientRateLimitProfile 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 setClientRateLimitProfile. 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.
setClientRateLimitProfile 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.