Enable or disable focus mode. When focus mode is enabled, only windows from the currently active process and its child processes are allowed to remain in the foreground.
AI agents invoke focus_mode 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 triggers an external operation that changes the windowing/display behavior of the cloud execution environment, affecting which processes can remain in the foreground. It modifies the runtime state of the environment rather than simply reading data or writing persistent data, making it an Execute-category action. Misuse could disrupt other running processes or UI interactions in the cloud environment.
From the tool's definition Enable or disable focus mode... only windows from the currently active process and its child processes are allowed to remain in the foreground
Documented attack patterns abuse exactly the kind of access focus_mode 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 focus_mode:
{
"version": "1",
"default": "deny",
"tools": {
"focus_mode": {
"limits": [
{
"counter": "focus_mode_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}focus_mode 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.
Enable or disable focus mode. When focus mode is enabled, only windows from the currently active process and its child processes are allowed to remain in the foreground. 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 focus_mode: 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.
focus_mode 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 focus_mode 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 focus_mode. 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.
focus_mode 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.