quit_app
Quit a running application by name. May cause unsaved work to be lost.
This record as markdown: /tools/heznpc-airmcp/quit-app.md
What quit_app does on AirMCP
AI agents call quit_app 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 quit_app is rated Critical
Forcibly terminating an application can result in irreversible loss of unsaved data and state. The description explicitly warns of potential data loss, making this a destructive action. The blast radius is high because quitting critical applications (e.g., a document editor, IDE, or system process) could cause significant and unrecoverable harm.
From the tool's definition Quit a running application by name. May cause unsaved work to be lost.
Attacks that exploit this kind of access
The rule that runs quit_app 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 quit_app, this is the rule to start with:
quit_app 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 quit_app call is checked against it from then on.
Questions about quit_app
Quit a running application by name. May cause unsaved work to be lost. 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 quit_app: 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.
quit_app 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 quit_app 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 quit_app. 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.
quit_app 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