list_running_apps
List all running applications with name, bundle identifier, PID, and visibility.
This record as markdown: /tools/heznpc-airmcp/list-running-apps.md
What list_running_apps does on AirMCP
AI agents call list_running_apps to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_running_apps is rated Low
This tool queries the system state to retrieve information about currently running processes. It performs a read-only operation with no ability to modify, execute, or delete anything. The blast radius is minimal—disclosure of running apps could inform an attacker about system state but cannot directly cause harm.
From the tool's definition Tool name 'list_running_apps' and description 'List all running applications with name, bundle identifier, PID, and visibility' indicates data retrieval only.
Attacks that exploit this kind of access
The rule that runs list_running_apps 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 list_running_apps, this is the rule to start with:
list_running_apps is read-only, so it stays allowed. 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 list_running_apps call is checked against it from then on.
Questions about list_running_apps
List all running applications with name, bundle identifier, PID, and visibility. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.
Register the Air MCP server in PolicyLayer and add a rule for list_running_apps: 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.
list_running_apps is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_running_apps 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 list_running_apps. 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.
list_running_apps 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