This record as markdown: /tools/io-github-heznpc-iconnect/minimize-window.md
What minimize_window does on Iconnect
AI agents invoke minimize_window to trigger actions in Iconnect. 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.
Why minimize_window is rated High
This tool performs a window management operation (minimize or restore), which is an external UI action rather than a pure data read or write. It affects the running state of applications on the system. Misuse is low-severity as it only affects window visibility, not data integrity or finances.
From the tool's definition 'Minimize or restore a window' — triggers a UI/window management action on the macOS desktop environment
Attacks that exploit this kind of access
The rule that runs minimize_window safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every minimize_window call is checked against it from then on.
Questions about minimize_window
Minimize or restore a window. It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iconnect 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 Iconnect. Nothing to install.
minimize_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 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.
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.
minimize_window is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
Across the catalogue