This record as markdown: /tools/io-github-heznpc-iconnect/system-power.md
What system_power does on Iconnect
AI agents invoke system_power 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 system_power is rated High
While shutdown/restart technically cannot be undone once initiated (suggesting Destructive), the primary classification is Execute because the tool's function is to trigger a system command/operation whose effects depend on the argument (shutdown vs. restart). The high severity reflects that misuse would disable the entire system, causing significant disruption.
From the tool's definition Tool description states 'Shutdown or restart the Mac' — these are system-level operations that trigger external procedures with irreversible immediate effects on system state.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_power 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 system_power, this is the rule to start with:
system_power 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 system_power call is checked against it from then on.
Questions about system_power
Shutdown or restart the Mac. Use with caution. 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 system_power: 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.
system_power 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 system_power 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 system_power. 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.
system_power 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