Set a specific window to fullscreen mode by its window ID.
AI agents invoke fullscreen_window 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 (changing window display state to fullscreen) in a cloud execution environment. It modifies the UI state of a running window, which is an action with side effects, though limited in blast radius. It fits Execute as it manipulates a running environment's window state rather than simply reading data or writing persistent data.
From the tool's definition Set a specific window to fullscreen mode by its window ID
Documented attack patterns abuse exactly the kind of access fullscreen_window 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 fullscreen_window:
{
"version": "1",
"default": "deny",
"tools": {
"fullscreen_window": {
"limits": [
{
"counter": "fullscreen_window_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}fullscreen_window 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.
Set a specific window to fullscreen mode by its window ID. 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 fullscreen_window: 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.
fullscreen_window 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 fullscreen_window 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 fullscreen_window. 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.
fullscreen_window 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.