This record as markdown: /tools/io-github-heznpc-iconnect/toggle-wifi.md
What toggle_wifi does on Iconnect
AI agents invoke toggle_wifi to trigger actions in Iconnect. 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 toggle_wifi is rated High
Toggling WiFi is an external system operation with significant impact: disabling WiFi can disrupt all network-dependent services, cut off remote access, and affect running processes. It is not a simple data read/write but an execution of a system-level state change. Misuse by an AI agent could cause denial of connectivity, making severity high.
From the tool's definition Turn WiFi on or off — triggers an external system operation that changes network connectivity state
Attacks that exploit this kind of access
The rule that runs toggle_wifi safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For toggle_wifi, this is the rule to start with:
toggle_wifi 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 Iconnect, apply this rule, and every toggle_wifi call is checked against it from then on.
Questions about toggle_wifi
Turn WiFi on or off. It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iconnect MCP server in PolicyLayer and add a rule for toggle_wifi: 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 Iconnect. Nothing to install.
toggle_wifi 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 toggle_wifi 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 toggle_wifi. 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.
toggle_wifi is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
Across the catalogue