minimize_window

Minimize a window.

SERVERAos SOURCE@hybridlabor-api/aos

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hybridlabor-api-aos/minimize-window.md

WHAT IT DOES

What minimize_window does on Aos

AI agents invoke minimize_window to trigger actions in Aos. 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.

RISK

Why minimize_window is rated High

Minimizing a window is a UI state-changing action on the GNOME desktop, executed via D-Bus. It is not a simple data read, nor does it delete data, but it does trigger an external operation whose effect (hiding a window) depends on the argument (which window to minimize). This fits the Execute category. Severity is medium because misuse could disrupt user workflow by hiding active windows, but it is reversible.

From the tool's definition Minimize a window — triggers an external desktop operation (window state change) via D-Bus automation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs minimize_window safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For minimize_window, this is the rule to start with:

minimize_window Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "minimize_window": {
      "limits": [
        {
          "counter": "minimize_window_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every minimize_window call is checked against it from then on.

FAQ

Questions about minimize_window

What does the minimize_window tool do? +

Minimize a window. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on minimize_window? +

Register the Aos MCP server in PolicyLayer and add a rule for minimize_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 Aos. Nothing to install.

What risk level is minimize_window? +

minimize_window is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit minimize_window? +

Yes. Add a rate_limit block to the minimize_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 minimize_window completely? +

Set action: deny in the PolicyLayer policy for minimize_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 minimize_window? +

minimize_window is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools → High-risk tools on this server →

Across the catalogue

focus_window on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →