This record as markdown: /tools/ikuai-mcp-server/kick-pppoe-user.md
What kick_pppoe_user does on Ikuai
AI agents invoke kick_pppoe_user to trigger actions in Ikuai. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why kick_pppoe_user is rated High
This tool terminates an active PPPoE user session on the router. It is an operational action that triggers an external effect (disconnecting a user), but it is not necessarily permanent/irreversible (the user can reconnect). It falls under Execute as it triggers an external operation. The blast radius is high because misuse could disrupt network access for legitimate users.
From the tool's definition 踢下线指定用户 — forcibly disconnects a specified PPPoE user session
Attacks that exploit this kind of access
The rule that runs kick_pppoe_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ikuai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kick_pppoe_user, this is the rule to start with:
kick_pppoe_user stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ikuai, apply this rule, and every kick_pppoe_user call is checked against it from then on.
Questions about kick_pppoe_user
踢下线指定用户. It is categorised as a Execute tool in the Ikuai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ikuai MCP server in PolicyLayer and add a rule for kick_pppoe_user: 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 Ikuai. Nothing to install.
kick_pppoe_user is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the kick_pppoe_user 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 kick_pppoe_user. 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.
kick_pppoe_user is provided by the Ikuai MCP server (gxxHuang/ikuai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ikuai, and thousands of servers like it.
Across the catalogue