terminate_macos_app_processes
Terminate running macOS processes matching an app name or bundle-related query without shell pipelines.
This record as markdown: /tools/cowork-os/terminate-macos-app-processes.md
What terminate_macos_app_processes does on CoWork OS
AI agents use terminate_macos_app_processes to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why terminate_macos_app_processes is rated Medium
An AI agent can call terminate_macos_app_processes faster than any human can review: one bad instruction and it creates or modifies resources in CoWork OS by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs terminate_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 terminate_macos_app_processes, this is the rule to start with:
terminate_macos_app_processes stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every terminate_macos_app_processes call is checked against it from then on.
Questions about terminate_macos_app_processes
Terminate running macOS processes matching an app name or bundle-related query without shell pipelines. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for terminate_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.
terminate_macos_app_processes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the terminate_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.
Set action: deny in the PolicyLayer policy for terminate_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.
terminate_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.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue