Manages windows, zoom, devtools, and webview state. Window actions: list, focus, minimize, maximize, unmaximize, close, show, hide, set_position, set_size, center, toggle_fullscreen. Zoom: set_zoom, get_zoom. DevTools: open_devtools, close_devtools, is_devtools_open. Webview state: clear_browsing...
AI agents invoke manage_window to trigger actions in Tauri Plugin. 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 external operations on the application's window and webview state. While some sub-actions are read-only (list, get_zoom, get_bounds, is_devtools_open), the most severe applicable actions include closing windows, clearing browsing data, opening devtools (which could expose sensitive state), and manipulating window visibility/position — all of which have side effects on the running application.
From the tool's definition Window actions: list, focus, minimize, maximize, unmaximize, close, show, hide, set_position, set_size, center, toggle_fullscreen. Zoom: set_zoom, get_zoom. DevTools: open_devtools, close_devtools.
Documented attack patterns abuse exactly the kind of access manage_window gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tauri Plugin, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_window:
{
"version": "1",
"default": "deny",
"tools": {
"manage_window": {
"limits": [
{
"counter": "manage_window_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}manage_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.
Manages windows, zoom, devtools, and webview state. Window actions: list, focus, minimize, maximize, unmaximize, close, show, hide, set_position, set_size, center, toggle_fullscreen. Zoom: set_zoom, get_zoom. DevTools: open_devtools, close_devtools, is_devtools_open. Webview state: clear_browsing_data, set_background_color, get_bounds, set_auto_resize. It is categorised as a Execute tool in the Tauri Plugin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tauri Plugin MCP server in PolicyLayer and add a rule for manage_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 Tauri Plugin. Nothing to install.
manage_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 manage_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 manage_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.
manage_window is provided by the Tauri Plugin MCP server (p3gleg/tauri-plugin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Tauri Plugin tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Tauri Plugin tools catalogued and risk-classified — across an index of 42,500+ MCP servers.