allow_sleep
Cancel any active prevent_sleep assertion immediately, so the Mac can sleep normally again (idle timeout or closing the lid). No-op if no assertion is active.
This record as markdown: /tools/heznpc-airmcp/allow-sleep.md
What allow_sleep does on AirMCP
AI agents call allow_sleep to permanently remove resources in AirMCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why allow_sleep is rated Critical
An AI agent that decides to call allow_sleep doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from AirMCP is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs allow_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 allow_sleep, this is the rule to start with:
allow_sleep is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every allow_sleep call is checked against it from then on.
Questions about allow_sleep
Cancel any active prevent_sleep assertion immediately, so the Mac can sleep normally again (idle timeout or closing the lid). No-op if no assertion is active. It is categorised as a Destructive tool in the AirMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Air MCP server in PolicyLayer and add a rule for allow_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.
allow_sleep is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the allow_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.
Set action: deny in the PolicyLayer policy for allow_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.
allow_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.
More on Air, and thousands of servers like it.
Across the catalogue