Critical Risk →

close_window

Close a specific window by its window ID.

How to control close_window ↓

What close_window does on Wuying AgentBay

AI agents call close_window to permanently remove resources in Wuying AgentBay — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why close_window needs a policy

Closing a window is an irreversible action that terminates the window and any unsaved state within it. The action cannot be undone once executed, making it Destructive. Severity is medium as it affects a single window session but could disrupt ongoing operations or lose unsaved work.

From the tool's definition Close a specific window by its window ID

Documented attack patterns abuse exactly the kind of access close_window gives an agent:

How to control close_window

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 close_window:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "close_window"
  ]
}

close_window disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Wuying AgentBay — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about close_window

What does the close_window tool do? +

Close a specific window by its window ID. It is categorised as a Destructive tool in the Wuying AgentBay MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on close_window? +

Register the Wuying AgentBay MCP server in PolicyLayer and add a rule for close_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.

What risk level is close_window? +

close_window is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit close_window? +

Yes. Add a rate_limit block to the close_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.

How do I block close_window completely? +

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

What MCP server provides close_window? +

close_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.

Enforce policy on every Wuying AgentBay tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.