find_macos_app_processes

Find running macOS processes matching an app name or bundle-related query without shell pipelines.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

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/cowork-os/find-macos-app-processes.md

WHAT IT DOES

What find_macos_app_processes does on CoWork OS

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

RISK

Why find_macos_app_processes is rated Low

The tool performs information retrieval about running processes. It does not execute commands, modify system state, delete data, or perform financial operations. While process information could theoretically be used maliciously in a larger attack chain, the tool itself is purely read-only with minimal blast radius.

From the tool's definition Tool description states 'Find running macOS processes matching an app name or bundle-related query' — this is a query/lookup operation that retrieves process information without modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find_macos_app_processes safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_macos_app_processes, this is the rule to start with:

find_macos_app_processes Allowed

find_macos_app_processes 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": {
    "find_macos_app_processes": {}
  }
}

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

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

FAQ

Questions about find_macos_app_processes

What does the find_macos_app_processes tool do? +

Find running macOS processes matching an app name or bundle-related query without shell pipelines. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_macos_app_processes? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for find_macos_app_processes: 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 CoWork OS. Nothing to install.

What risk level is find_macos_app_processes? +

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

Can I rate-limit find_macos_app_processes? +

Yes. Add a rate_limit block to the find_macos_app_processes 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 find_macos_app_processes completely? +

Set action: deny in the PolicyLayer policy for find_macos_app_processes. 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 find_macos_app_processes? +

find_macos_app_processes is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

The MCP Attack Database →

Guides

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