This record as markdown: /tools/heznpc-airmcp/toggle-focus-mode.md
What toggle_focus_mode does on AirMCP
AI agents invoke toggle_focus_mode 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.
Why toggle_focus_mode is rated High
This tool triggers an external system-level operation on macOS — enabling or disabling Focus/Do Not Disturb mode. It doesn't just read data or write a document; it changes OS-level notification behavior. The effect is reversible (can be toggled back), so it's not Destructive, but it does execute a system state change with real consequences (suppressing notifications). Execute is the appropriate category.
From the tool's definition Toggle Do Not Disturb (Focus mode) on or off
Attacks that exploit this kind of access
The rule that runs toggle_focus_mode 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 toggle_focus_mode, this is the rule to start with:
toggle_focus_mode 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 AirMCP, apply this rule, and every toggle_focus_mode call is checked against it from then on.
Questions about toggle_focus_mode
Toggle Do Not Disturb (Focus mode) on or off. 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.
Register the Air MCP server in PolicyLayer and add a rule for toggle_focus_mode: 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.
toggle_focus_mode 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_focus_mode 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_focus_mode. 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_focus_mode 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.
This server
Across the catalogue