AI agents call list_running_apps to retrieve information from Macos Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely enumerates currently running applications—a passive data retrieval operation. It has no side effects, does not execute code, modify system state, or delete data. Even in adversarial scenarios, listing running apps provides visibility but cannot directly compromise system integrity or trigger destructive actions. The low severity reflects minimal blast radius if misused by an agent.
From the tool's definition Tool name 'list_running_apps' and description 'List all visible running macOS applications' indicate a read-only query operation that retrieves information about running processes without modification or execution of external actions.
Documented attack patterns abuse exactly the kind of access list_running_apps gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Macos Control, and nothing reaches the server without passing your rules. This is the rule we recommend for list_running_apps:
{
"version": "1",
"default": "deny",
"tools": {
"list_running_apps": {}
}
}list_running_apps is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all visible running macOS applications. It is categorised as a Read tool in the Macos Control MCP Server, which means it retrieves data without modifying state.
Register the Macos Control 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 Macos Control. 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 Macos Control MCP server (peterhdd/macos-control-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Macos Control, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Macos Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.