List all running applications with their bundle IDs, names, and PIDs.
AI agents call app_list to retrieve information from ScreenHand without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about running processes (bundle IDs, names, PIDs) without side effects. It is a pure query operation that does not execute code, modify data, or trigger external actions. The low severity reflects minimal blast radius — an attacker gains visibility into running applications but cannot directly compromise them through this tool alone.
From the tool's definition Tool name is 'app_list' and description states it 'List all running applications' — a read-only enumeration of system state with no modification or execution of commands.
Documented attack patterns abuse exactly the kind of access app_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ScreenHand, and nothing reaches the server without passing your rules. This is the rule we recommend for app_list:
{
"version": "1",
"default": "deny",
"tools": {
"app_list": {}
}
}app_list 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 running applications with their bundle IDs, names, and PIDs. It is categorised as a Read tool in the ScreenHand MCP Server, which means it retrieves data without modifying state.
Register the ScreenHand MCP server in PolicyLayer and add a rule for app_list: 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 ScreenHand. Nothing to install.
app_list 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 app_list 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 app_list. 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.
app_list is provided by the ScreenHand MCP server (manushi4/screenhand). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ScreenHand, 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.
89 ScreenHand tools catalogued and risk-classified — across an index of 43,000+ MCP servers.