prevent_sleep

Prevent the Mac from sleeping for a specified duration using caffeinate. The assertion is transient — it auto-releases when the timer elapses; no manual stop is required.

SERVERAirMCP SOURCEairmcp

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/heznpc-airmcp/prevent-sleep.md

WHAT IT DOES

What prevent_sleep does on AirMCP

AI agents invoke prevent_sleep to trigger actions in AirMCP. 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 prevent_sleep is rated High

This tool runs the 'caffeinate' system command to modify the Mac's power management behavior. It executes an external system operation that affects OS-level settings for a period of time. While the effect is transient and auto-releases, it is still executing a system command with real side effects (preventing sleep), making it Execute rather than Write.

From the tool's definition "Prevent the Mac from sleeping for a specified duration using caffeinate"

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs prevent_sleep safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For prevent_sleep, this is the rule to start with:

prevent_sleep Rate-limited

prevent_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": {
    "prevent_sleep": {
      "limits": [
        {
          "counter": "prevent_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 AirMCP, apply this rule, and every prevent_sleep call is checked against it from then on.

FAQ

Questions about prevent_sleep

What does the prevent_sleep tool do? +

Prevent the Mac from sleeping for a specified duration using caffeinate. The assertion is transient — it auto-releases when the timer elapses; no manual stop is required. It is categorised as a Execute tool in the AirMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on prevent_sleep? +

Register the Air MCP server in PolicyLayer and add a rule for prevent_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 AirMCP. Nothing to install.

What risk level is prevent_sleep? +

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

Can I rate-limit prevent_sleep? +

Yes. Add a rate_limit block to the prevent_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 prevent_sleep completely? +

Set action: deny in the PolicyLayer policy for prevent_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 prevent_sleep? +

prevent_sleep is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Air, and thousands of servers like it.

This server

All 279 Air 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 →