list_running_apps

List all running applications with name, bundle identifier, PID, and visibility.

SERVERIconnect SOURCEiconnect-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/list-running-apps.md

WHAT IT DOES

What list_running_apps does on Iconnect

AI agents call list_running_apps to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_running_apps is rated Low

This tool retrieves information (running app names, bundle IDs, PIDs, visibility status) without modifying or executing anything. However, it reveals sensitive system state that could inform reconnaissance—an attacker could enumerate running security tools, debuggers, or monitoring software to plan evasion.

From the tool's definition Tool description states it 'List[s] all running applications' — a pure query operation retrieving system state with 'no side effects'. The verb 'list' and the read-only nature of enumerating running processes confirm this is a Read category tool.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_running_apps safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, 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 Allowed

list_running_apps is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_running_apps": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every list_running_apps call is checked against it from then on.

FAQ

Questions about list_running_apps

What does the list_running_apps tool do? +

List all running applications with name, bundle identifier, PID, and visibility. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_running_apps? +

Register the Iconnect 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 Iconnect. Nothing to install.

What risk level is list_running_apps? +

list_running_apps is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_running_apps? +

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.

How do I block list_running_apps completely? +

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.

What MCP server provides list_running_apps? +

list_running_apps is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →