Start a specified application using the provided command and optional working directory. Returns a list of processes associated with the launched application, including their process names, PIDs, and startup commands.
AI agents invoke start_app to trigger actions in Wuying AgentBay. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool allows launching arbitrary applications with user-controlled commands in a cloud execution environment. While not inherently destructive, the blast radius is significant: a compromised or misdirected agent could launch malicious processes, resource-intensive applications, or tools that interact with external systems.
From the tool's definition Tool description states it 'Start[s] a specified application using the provided command' and 'Returns a list of processes associated with the launched application'.
Documented attack patterns abuse exactly the kind of access start_app gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wuying AgentBay, and nothing reaches the server without passing your rules. This is the rule we recommend for start_app:
{
"version": "1",
"default": "deny",
"tools": {
"start_app": {
"limits": [
{
"counter": "start_app_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}start_app stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Start a specified application using the provided command and optional working directory. Returns a list of processes associated with the launched application, including their process names, PIDs, and startup commands. It is categorised as a Execute tool in the Wuying AgentBay MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wuying AgentBay MCP server in PolicyLayer and add a rule for start_app: 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 Wuying AgentBay. Nothing to install.
start_app is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_app 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 start_app. 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.
start_app is provided by the Wuying AgentBay MCP server (michael98671/agentbay). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wuying AgentBay, 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.
59 Wuying AgentBay tools catalogued and risk-classified — across an index of 43,000+ MCP servers.