system_sleep

Put the Mac to sleep.

SERVERIconnect SOURCEiconnect-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/system-sleep.md

WHAT IT DOES

What system_sleep does on Iconnect

AI agents invoke system_sleep 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.

RISK

Why system_sleep is rated High

Putting the Mac to sleep is an external system operation that affects the running state of the entire machine. It is not purely destructive (no data is deleted), but it executes a privileged OS-level action with broad blast radius: all running processes are suspended, network connections drop, and any unsaved work may be at risk.

From the tool's definition 'Put the Mac to sleep' — triggers a system-level power state change on the host machine

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs system_sleep 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_sleep, this is the rule to start with:

system_sleep Rate-limited

system_sleep 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "system_sleep": {
      "limits": [
        {
          "counter": "system_sleep_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every system_sleep call is checked against it from then on.

FAQ

Questions about system_sleep

What does the system_sleep tool do? +

Put the Mac to sleep. 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.

How do I enforce a policy on system_sleep? +

Register the Iconnect MCP server in PolicyLayer and add a rule for system_sleep: 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.

What risk level is system_sleep? +

system_sleep is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit system_sleep? +

Yes. Add a rate_limit block to the system_sleep 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.

How do I block system_sleep completely? +

Set action: deny in the PolicyLayer policy for system_sleep. 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.

What MCP server provides system_sleep? +

system_sleep 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.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →